Systems and methods providing predictive analyses of events relating to emergency power supply systems

ABSTRACT

Aspects of the present disclosure generally relate to systems and methods for managing and monitoring a plurality of emergency power supply systems (EPSS&#39;s) at a facility via an emergency power management system (EPMS). The EPMS generally comprises EPSS equipment, a management computer system for managing, monitoring, and testing the operational characteristics of the EPSS equipment, and a plurality of interface modules for providing unified communication capabilities between the management computer system and the EPSS equipment. Additional aspects relate to methods for easily and efficiently creating and installing an EPMS at a facility. Further aspects are directed to providing predictive analyses related to the EPSS equipment. Also, aspects of the present disclosure relate to normalizing EPSS equipment information across varying vendors, makes, and models of equipment so as to provide a unified view of all equipment across a given facility.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part and claims benefit under 35U.S.C. §120 of U.S. patent application Ser. No. 11/556,496, filed Nov.3, 2006, and entitled “Power Monitoring and Testing”, now U.S. Pat.No.______, which claims benefit under 35 U.S.C. §119(e) of U.S.Provisional Patent Application No. 60/823,474, filed Aug. 24, 2006, andentitled “Test and Monitoring System”, each of which are incorporatedherein by reference in their entirety.

TECHNICAL FIELD

The present systems, methods, and devices relate generally to industrialautomation systems, and more particularly to managing, monitoring, andtesting emergency power supply systems.

BACKGROUND

Many facilities require backup power systems to generate power in caseof emergencies or when conventional power systems fail. These backuppower systems, commonly referred to as emergency power supply systems(EPSS's), provide power to a facility when utility power is unavailable.Loss of utility power may be due to any number of causes, such as downedpower lines, planned blackouts, malfunctions at a sub-station, inclementweather, and the like. When these or other similar events occur, EPSS'sare activated to supply much needed power to a facility.

For some facilities, loss of power is merely an inconvenience. For otherfacilities, however, it is absolutely crucial to have a reliable sourceof backup power in case of a power failure. For example, hospitals mustoperate life-sustaining equipment around the clock, so if power if lost,a backup power source must begin generating power immediately. Also, aloss of power during a medical operation would likely have severeresults, including potential death of the patient. Airports and otherports require uninterrupted power as well so that there are nodisturbances during dangerous procedures such as takeoffs, landings, andthe like. Further, it may be important for a military base to sustaincontinuous power to avoid any security breaches, weapons malfunctions,etc. Many other facilities may require emergency power supply systems aswell, such as universities, government structures, communicationsservice installations, data processing centers, and office buildings, toname only a few.

In its basic form, an EPSS includes a power generator (also referred toas an engine-generator or genset), an automatic transfer switch (ATS),and a fuel supply. Essentially, when a utility power disruption eventoccurs, the ATS detects the disruption and sends a signal to thegenerator to begin running. The generator (or genset) typically includesa mechanical energy source, such as an internal combustion engine,coupled with an electrical generator. The mechanical energy sourceoperates on fuel from the fuel supply, and the electrical generatorconverts the mechanical energy from the mechanical energy source intoelectrical power. Once the generator reaches a sufficient power level,the ATS transfers the power to the facility (or a certain portion of thefacility) from utility power to generator-supplied power. Preferably,and in many EPSS's, this transfer occurs quickly, such that no realpower disturbance is felt at the facility.

While some EPSS's include only one generator, ATS, and fuel supply,other EPSS's incorporate multiple generators, ATS's and otherswitchgear, and fuel supplies. Additionally, most facilities requiremany EPSS's to operate different rooms and buildings across the facilityin case of a power disruption. Thus, any given facility may include tensor even hundreds of items of EPSS equipment at the facility. Obviously,managing such a vast amount of equipment spread across acres or evenmiles of a facility is a tremendous challenge. For example, the EPSSequipment must be maintained, fuel levels must be continuouslymonitored, connections and wiring should be examined, the equipmentshould be regularly checked and tested to ensure it is functioningproperly, etc. Traditionally, this equipment is monitored and supervisedby hand by employees who periodically physically check the equipment toensure it is operating appropriately. However, humans can often makemistakes, and fail to notice vital problems with the EPSS equipment. Or,the equipment may break or experience a malfunction between checks,during which time a power loss may occur. Further, given the vast sizeof many facilities, sheer limitations on experienced personnel mayprevent a facility from adequately managing its vital EPSS equipment.

Additionally, some facilities, especially hospitals, are required byvarious regulatory bodies to test their EPSS equipment regularly. Thesetests are completed for compliance purposes to ensure the equipment isoperating correctly in case of an emergency. Generally, these tests aredone manually by a facility employee who physically goes to each EPSSand manually tests the ATS which in turn starts and tests the supportinggenerator(s). The employee then tracks certain parameters of theequipment, such as voltage and current output, frequency, exhausttemperature of the mechanical energy source, and various other measures.Because this testing is done by hand, it is inefficient, inaccurate, andcumbersome, and often some tests are overlooked or simply ignored.

Further, during a power outage or crisis event, there is traditionallyno way to actively monitor the status of running or standby EPSSequipment without physically going to the equipment and checking on it.For instance, during a mass power outage, and entire facility may losepower. Hopefully, the EPSS's will startup and begin supplying power tothe facility, but some of the EPSS's may fail to operate due to anequipment malfunction, such as starting battery failure, empty fuelsupply, or some other reason. Thus, the portion of the facility that wasintended to be powered by the inoperative EPSS's would remain withoutpower. It may be important to immediately identify which EPSS's failedto operate so that the problem can be quickly diagnosed and corrected.However, without a system to monitor the status of all of the facility'sEPSS's in real time, certain portions of the facility may go withoutpower for hours or longer.

Moreover, if a power outage or crisis event persists for an extendedperiod of time, then it becomes increasingly important to be able tomonitor the current status of all EPSS's during the crisis to ensurethey are operating correctly, that no equipment problems are surfacing(such as excess temperatures or pressures within the equipment), thatthere is enough fuel available to continue operating most or all ofthem, etc. However, many EPSS's today provide no way to monitor, view,collect data from, or check on equipment in real time during anemergency power disruption event.

To complicate matters, most facilities have acquired different types,brands, and models of EPSS equipment over time as the facility hasexpanded. Thus, any given facility may employ a variety of differentmodels of generators, ATS's, and other equipment, all of which were madeby different vendors or manufacturers, and which were made at differentpoints in time. For instance, one building on a university campus mayincorporate backup power supplied by one brand of generators that wasmanufactured decades ago, while the building right next door might useanother brand of generator that was manufactured last year. Thisvariance in equipment further hinders the facility's ability to manage,maintain, and test the equipment because each piece of equipmentfunctions differently, has different acceptable running parameters,requires different testing procedures, looks different, soundsdifferent, etc. Thus, adequately maintaining and monitoring all of afacility's EPSS equipment with a manual labor force becomes virtuallyimpossible.

Therefore, there is a long-felt but unresolved need for a system ormethod that enables a system operator to actively, in real time,monitor, test, and control a plurality of EPSS's across varyinglocations within a facility. There is a further need for a system thatallows monitoring, normalizing of data, and easy and efficient testingof different makes and models of EPSS equipment in a real-time manner.Also, the system should have capability for quick and easy installationat a facility, be equipment vendor neutral, and provide any requiredtesting or compliance reports in virtually real time.

BRIEF SUMMARY OF THE DISCLOSURE

Briefly described, and according to on embodiment, a method is describedherein for configuring one or more pre-existing emergency power supplysystems (EPSS's) distributed amongst many locations at a facility toprovide an emergency power management system (EPMS). Generally, the EPMSincludes a management computer system for managing operationalcharacteristics of the EPMS. In one aspect, the management computersystem receives EPSS inventory information input by an operatorcorresponding to properties of EPSS equipment that is physically presentin the locations within the site. That EPSS inventory information isstored in a database and a plurality of inventoried EPSS's are defined.Then, the EPSS inventory information is processed via business rulesengine software according to one or more predefined business rules togenerate: (a) a bill of materials for EPMS hardware and data acquisitionequipment required to collect EPSS operational data from the inventoriedEPSS equipment, and (b) one or more order documents for installing theEPMS hardware and data acquisition equipment from the bill of materialsat the site. Next, the EPMS hardware and data acquisition equipment areinstalled on or around the inventoried EPSS equipment according to theone or more order documents. Finally, one or more interface modules areinstalled at the site to operatively connect the installed dataacquisition equipment to the management computer system and to provide acommunication link between the management computer system and theinventoried EPSS's, whereby an operative and configured EPMS isprovided.

According to one aspect, the order documents include work ordersdetailing work required to install the EPMS hardware and dataacquisition equipment from the bill of materials at the site. The orderdocuments also include engineering schematics for use by installationpersonnel to connect the inventoried EPSS equipment to the EPMS hardwareand data acquisition equipment and to the management computer system. Inone aspect, the order documents further include a configuration file forconfiguring management software to enable the management computer systemto operate with the data acquisition equipment. The order documentsadditionally include one or more vendor orders for purchase of the EPMShardware and data acquisition equipment from the bill of materials fromone or more vendors. In a further aspect, the order documents include aproject plan describing timelines and tasks associated with installingand configuring the EPMS at the site.

According to another aspect, the order documents are automaticallycommunicated by the management computer system to installation personnelto install the EPMS hardware and data acquisition equipment at the site.

In some aspects, a price quote is generated by the business rules enginesoftware for configuring the EPMS at the site.

According to yet another aspect, the EPSS inventory information isgathered by the operator via a portable data collection device.

According to still another aspect, the properties of the EPSS equipmentinclude an equipment manufacturer, equipment model, and one or morerated values for each item of EPSS equipment. The properties of the EPSSequipment may also include specific physical attributes of the EPSSequipment that dictate which specific EPMS hardware and data acquisitionequipment is required for configuring the EPMS. In one aspect, theproperties of the EPSS equipment further include a physical positionindicative of suitability for installation of EPMS hardware and dataacquisition equipment on or around the one or more items of EPSSequipment.

According to an additional aspect, the management computer systemfurther includes one or more servers for carrying out processingoperations of the management computer system.

In a further aspect, the EPSS equipment includes generators, automatictransfer switches (ATS's), switchgear, fuel supplies, and fuelmanagement systems. In some aspects, the EPSS equipment is manufacturedto include some or all of the required EPMS hardware and dataacquisition equipment, such that no installation (or only minimalinstallation) of such equipment is needed.

According to one embodiment, a user of the EPMS may view stored EPSSinventory information associated with the site via an online portal.

According to yet another aspect, the data acquisition equipment includesmonitoring sensors (such as thermocouples, resistive temperaturedetectors (RTDs), pressure senders, current transformers (CTs), andlimit switches), connectors required by particular types of monitoringsensors, power supplies, fuel gauges, power meters, gauges, statusindicators, viewing cameras, microphones, vibration sensors, inertialsensors, motion sensors, actuation components, solenoids, and relays,and any other equipment necessary to collect operational data from theEPSS equipment.

According to still another aspect, the EPMS hardware includes mountingracks, mounting hardware, and communication links (such as cables, fiberoptics, wiring, and wireless equipment), and any other hardwarenecessary to install and configure an EPMS at the site.

In another embodiment, an emergency power management system (EPMS) isdisclosed for managing one or more pre-existing emergency power supplysystems (EPSS's) at a site. The EPMS generally includes data acquisitionequipment for collecting EPSS operational information from the EPSSequipment at the site. In one aspect, the data acquisition equipment iscapable of collecting EPSS operational information from EPSS equipmentmanufactured by a plurality of manufacturers. The EPMS also includes oneor more interface modules operatively connected to the data acquisitionequipment for receiving the EPSS operational information from dataacquisition equipment and normalizing the EPSS operational informationto allow for efficient subsequent processing. The EPMS additionallyincludes a management computer system operatively connected to the oneor more interface modules for receiving the normalized EPSS operationalinformation from the interface modules and storing the normalized EPSSoperational information in one or more databases. The managementcomputer system includes management software for processing thenormalized EPSS operational information into an interactive display andpresenting the interactive display to a user via a user interface. Inone aspect, the interactive display enables the user to manage the EPSSequipment at the site.

According to one aspect, the EPSS equipment includes generators,automatic transfer switches (ATS's), switchgear, fuel supplies, and fuelmanagement systems. For a generator, the EPSS operational informationincludes the jacket water temperature, exhaust temperature, oilpressure, oil temperature, coolant temperature, battery chargingvoltage, battery charging current, engine running status, engine “not inauto” status, engine runtime, engine speed, generator power, rated load,generator power factor, percent generator capacity, three-phase voltage,three-phase current, generator frequency, and applied torque.

According to another aspect, the EPSS operational information for an ATSincludes the emergency power, emergency power factor, emergencyfrequency, emergency three-phase voltage, emergency three-phase current,emergency average current, emergency power hours, normal power, normalpower factor, normal frequency, normal three-phase voltage, normalthree-phase current, normal average current, normal power hours,emergency power status, normal power status, emergency breaker status,and normal breaker status.

According to a further aspect, the EPSS operational information for afuel supply includes the fuel level, fuel supply status, and exit fuelflow rate.

In one aspect, each of the one or more interface modules includes amicroprocessor, memory, communication bus, one or more data inputs, oneor more data outputs, and interface module software for carrying out thefunctions of receiving, normalizing, and transmitting EPSS operationalinformation from the data acquisition equipment to the managementcomputer system. In one aspect, an interface module is a remote terminalunit. In another aspect, an interface module is a programmable logiccontroller (PLC). Generally, each of the interface modules includes afirewall for preventing unauthorized access to the EPSS equipment, themanagement computer system, or the EPSS operational information.

In yet another aspect, the management computer system includes serversfor carrying out the operational processes of the EPMS. In on aspect,the management computer system logs historical EPSS operationalinformation in the one or more databases for providing operationaltrends of the one or more items of EPSS equipment over time.

In still another aspect, the interactive display that is displayed tothe user via the user interface is a chart or graph of one or more itemsof EPSS operational information plotted over a predefined time period.In another aspect, the interactive display is one or more visualpictures of the EPSS equipment to enable visual monitoring of the EPSSequipment at the site. In one aspect, the interactive display is aninteractive map view of the EPSS equipment for enabling a site-wide viewof the pre-existing EPSS's at the site. In a further aspect, theinteractive display is a report detailing specific normalized EPSSoperational information for one or more selected items of EPSS equipmentfor a predetermined time period. In still further aspects, theinteractive display is an electrical one-line view of power connectionsof the EPSS equipment at the site to utility power or emergency power.

According to an additional aspect, the user interface displays an alarmto the user when one or more predefined conditions related to the EPSSoperational information are satisfied. The predefined conditionsgenerally include when one or more values of EPSS operationalinformation exceeds one or more predetermined values, when one or morevalues of EPSS operational information falls below one or morepredetermined values, and when EPSS equipment malfunctions.

According to one aspect, the user interface displays normalized EPSSoperational information related to a power disruption event as the eventis occurring. The power disruption event may be a planned or unplannedloss of utility power, including an emergency or test.

Typically, according to a further aspect, the management computer systemprovides user security to prevent unauthorized access to the EPMS.

According to another embodiment, a method is described herein fortesting emergency power supply system (EPSS) equipment at a facility.Generally, the EPSS equipment includes at least one automatic transferswitch (ATS), and the EPSS equipment is operatively connected to an EPSSmanagement computer system for managing the EPSS equipment. In oneaspect, the EPSS management computer system receives a test initiationcommand for initiation of a test of one or more items of EPSS equipment.In one aspect, the test initiation command is generated by a user via agraphical user interface (GUI), and the test initiation command includesone or more testing parameters. Upon receipt of the test initiationcommand, the EPSS management computer system creates a data record foreach of the items of EPSS equipment that are subject to the test. Eachdata record includes EPSS testing data related to the automatic loadtest, and each data record is stored in a database. Then, a test startcommand is sent from the EPSS management computer system to aninitiating ATS to start the automatic load test as a function of the oneor more testing parameters in the test initiation command. Generally,the initiating ATS facilitates a transfer of electrical power to aportion of the facility from utility power to emergency power. Duringthe test, the EPSS testing data is received from the EPSS equipment andstored in a data record for use in generating one or more test reports.Once the test has ended, the power to the portion of the facility istransferred back to utility power and the one or more test reports aregenerated based on the stored data records.

According to one aspect, the EPSS equipment further includes at leastone fuel supply and at least one fuel management system. In anotheraspect, the EPSS equipment includes switchgear.

In yet another aspect, the EPSS equipment further includes at least onegenerator. For a generator, the EPSS testing data that is received fromthe generator and stored in a corresponding generator data recordincludes a test start date and time, test end date and time, time anddate generator begins running, time and date generator stops running,total engine runtime, time duration of generator cooldown, oil pressure,coolant temperature, exhaust temperature, charging voltage, chargingcurrent, power, facility load powered, rated power, percent of ratedpower, three-phase voltage, three-phase current, and frequency. In oneaspect, the data record for the generator includes a generatoridentifier, test identifier, facility identifier, user information,identifier of one or more EPSS's being tested, group of EPSS equipmentto be tested, test type, and a creation date and time of the datarecord.

According to a further aspect, the testing parameters in the testinitiation command include the duration of the test, group of EPSSequipment to be tested, test type (such as a one-time test, periodictest, and compliance test), the initiating ATS, load test transfer timeoffset, and a designation that the at least one generator must provideemergency power equal to at least 30% of its rated load before testrecording begins.

In still another aspect, for an ATS, the EPSS testing data that isreceived from the at least one ATS and stored in a corresponding ATSdata record is selected from the group comprising: date and timeinitiation command is received, test start date and time, date and timefacility power is transferred from utility power to emergency power,time duration of transfer from utility power to emergency power, dateand time facility power is transferred back from emergency power toutility power, time duration of transfer from emergency power to utilitypower, test end date and time, three-phase voltage, three-phase current,total current, rated current, percent of rated current, power factor,total power, facility load powered, frequency, and a percent of ratedpower for generators connected to the at least one ATS. In one aspect,the data record for the ATS includes an ATS identifier, a testidentifier, facility identifier, user information, identifier of one ormore EPSS's being tested, the initiating ATS, group of EPSS equipment tobe tested, test type, and a creation date and time of the data record.

According to one aspect, the test start command is sent from the EPSSmanagement computer system to the initiating ATS through an interfacemodule. Generally, the interface module is operatively connected to theEPSS equipment for transmitting signals from the EPSS managementcomputer system to the EPSS equipment to operate the EPSS equipment. Inone aspect, the interface module receives EPSS testing data from theEPSS equipment during the test and normalizes and transmits the EPSStesting data to the EPSS management computer system for use ingenerating the one or more test reports.

In another aspect, a record of the specific ATS's that have been used asinitiating ATS's for initiating tests during a predefined time period islogged in a database. Then, the system user is provided with a suggestedinitiating ATS via the GUI corresponding to an ATS that has not beenused as an initiating ATS during the predefined time period so as toensure all ATS's at the facility are adequately tested.

According to one aspect, once an emergency event is detected at thefacility, the test is aborted.

According to a further aspect, live EPSS testing data is displayed tothe user via the GUI as the test is occurring.

According to an additional aspect, the EPSS management computer systemmaintains a schedule of tests for running tests of the EPSS equipmentaccording to a calendar of tests. In one aspect, the EPSS managementcomputer system maintains a calendar of historical tests for viewingEPSS testing data related to past tests.

In yet another aspect, the one or more test reports comprise one or morecompliance reports for complying with regulatory testing requirements ofthe EPSS equipment. In one aspect, the regulatory testing requirementsare mandated by the Joint Commission and set by the National FireProtection Agency. In still another aspect, the EPSS management computersystem retrieves a beginning test data point, middle test data point,and ending test data point for the automatic load test from the EPSStesting data stored in the data records for each of the items of EPSSequipment for inclusion in the one or more compliance reports.

In a further aspect, the one or more test reports comprise one or moreoperational reports listing one or more items from the EPSS testing datareceived during the automatic load test for a plurality of test datapoints for each of items of EPSS equipment.

According to another aspect, the EPSS management computer systemprovides an alarm to the user via the GUI when one or more predefinedoccurrences related to the EPSS equipment occurs during a test. In oneaspect, the one or more predefined occurrences include when one or moreEPSS testing data values exceeds one or more predetermined values, whenone or more EPSS testing data values falls below one or morepredetermined values, when one or more items of EPSS equipmentmalfunctions, and when one or more items of EPSS equipment fails tooperate.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate one or more embodiments of thedisclosure and, together with the written description, serve to explainthe principles of the disclosure. Wherever possible, the same referencenumbers are used throughout the drawings to refer to the same or likeelements of an embodiment, and wherein:

FIG. 1 is an overview of an embodiment of an emergency power managementsystem.

FIG. 2 shows a block diagram of another embodiment of an emergency powermanagement system.

FIG. 3 is a block diagram illustrating an embodiment of a server.

FIG. 4 is a block diagram of yet another embodiment of an emergencypower management system.

FIG. 5 illustrates a block diagram of various software entities,modules, and other similar elements, including call flows and securityidentities according to one embodiment of the present system.

FIG. 6 shows a block diagram of enterprise-wide server software systementities modules, and other similar elements, including call flows andsecurity identities according to one embodiment of the present system.

FIG. 7 is a terminal display showing one embodiment of an interactivemap view for viewing multiple EPSS's at a given facility.

FIG. 8 shows a sample terminal display of EPSS equipment statusaccording to an embodiment of the present system.

FIG. 9 is a terminal display depicting one embodiment of a testscripting interface for testing EPSS equipment at a given facility.

FIG. 10 illustrates a sample terminal display of one embodiment of atest scheduling and status interface for testing EPSS equipment at agiven facility.

FIG. 11 shows a terminal display of a calendar view of a test schedulinginterface according to one embodiment of the present system.

FIG. 12 illustrates one embodiment of a test report for a test of EPSSequipment at a given facility.

FIG. 13 is a sample terminal display showing a statistical analysis ofEPSS operational data at a given facility according to one embodiment ofthe present system.

FIG. 14 is a sample terminal display showing alarm managementfunctionalities according to one embodiment of the present system.

FIG. 15 shows a sample terminal display of alarm histories for variousitems of EPSS equipment at a facility according to one embodiment of thepresent system.

FIG. 16 illustrates a sample terminal display of a logging groupconfiguration interface according to an embodiment of the presentsystem.

FIG. 17 is an overhead view of a sample facility including multipleEPSS's.

FIG. 18 illustrates a flow chart of one embodiment of the steps involvedin system design automation for creating and installing an emergencypower management system at a facility or site.

FIG. 19A shows a sample display of a site survey tool used forcollecting generator information according to one embodiment of thepresent system.

FIG. 19B illustrates a sample display of a site survey tool used forcollecting ATS information according to one embodiment of the presentsystem.

FIG. 20 shows a sample display for a facility portal according to oneembodiment of the present system.

FIG. 21A is a sample generator inventory report created by the inventoryreport generation field contained in an embodiment of the facilityportal.

FIG. 21B shows a sample ATS inventory report created by the inventoryreport generation field contained in an embodiment of the facilityportal.

FIG. 21C is a sample fuel tank inventory report created by the inventoryreport generation field contained in an embodiment of the facilityportal.

FIG. 22A illustrates a sample ATS manufacturer report created by theinventory report generation field contained in an embodiment of thefacility portal.

FIG. 22B shows a sample generator manufacturer report created by theinventory report generation field contained in an embodiment of thefacility portal.

FIG. 23 is a diagram illustrating an embodiment of an installed andoperative emergency power management system at a facility.

FIG. 24A illustrates a terminal display of a tabular site summary viewfor a sample site according to an embodiment of the present system.

FIG. 24B shows a terminal display of a map site summary view for asample site according to an embodiment of the present system.

FIG. 25A is a terminal display of a tabular EPSS view for a sample EPSSaccording to an embodiment of the present system.

FIG. 25B illustrates a terminal display of a one-line view for a givenEPSS according to an embodiment of the present system.

FIG. 26 shows a terminal display of an entity detail view for aparticular ATS and particular generator in a given EPSS according to anembodiment of the present system.

FIG. 27 illustrates an embodiment of a combined multimedia display forshowing live audio and video feeds for a plurality of generators andother EPSS equipment over a plurality of EPSS's at a site or facility.

FIG. 28 is a terminal display of an EPSS equipment roll-up view listingall items of EPSS equipment at a given site according to an embodimentof the present system.

FIG. 29 is a terminal display of a fuel system summary for a fuel tankthat supplies EPSS equipment at a site according to an embodiment of thepresent system.

FIG. 30A is a flow chart showing the basic functional operations of oneembodiment of the interface module to receive, normalize, and transmitEPSS operational data to the management computer system.

FIG. 30B is a flow chart showing the basic functional operations of oneembodiment of the interface module to receive testing and controlcommands from the management computer system and transmit those commandsto the EPSS equipment.

FIG. 31 shows a terminal display of an embodiment of a test setup screenfor testing items of EPSS equipment.

FIG. 32 illustrates a flow chart listing the steps involved in oneembodiment of a testing process for testing EPSS equipment.

FIG. 33 is a flow chart listing the steps involved in one embodiment ofa process for using an emergency event as a valid test of EPSSequipment.

FIG. 34A is a sample generator operational report for a test of a givengenerator within an EPSS according to an embodiment of the presentsystem.

FIG. 34B shows a sample generator compliance report for a test of agiven generator within an EPSS according to an embodiment of the presentsystem.

FIG. 34C illustrates a sample ATS operational report for a test ofseveral ATS's within an EPSS according to an embodiment of the presentsystem.

FIG. 34D is a sample ATS compliance report for a test of several ATS'swithin an EPSS according to an embodiment of the present system.

FIG. 35A is a sample emergency events report listing emergency eventsthat have occurred for each generator at a facility over a given timeperiod according to an embodiment of the present system.

FIG. 35B shows a sample generator loaded runs report listing all loadeduses of each generator at a facility over a given time period accordingto an embodiment of the present system.

FIG. 35C illustrates a sample generator run times report showing all runtimes of each generator at a facility over a given time period accordingto an embodiment of the present system.

FIG. 35D is a sample switch operation report listing all transfersbetween normal and emergency power for one or more ATS's at a facilityover a given time period according to an embodiment of the presentsystem.

FIG. 36 shows an embodiment of an interactive calendar display fordisplaying future scheduled tests and past power disruption events for agiven facility.

Appendix I shows a sample bill of materials listing all necessary itemsrequired for installation and integration of an embodiment of anemergency power management system at a site.

Appendix II illustrates sample work instructions for installing dataacquisition equipment and EPMS hardware at a site.

Appendix III illustrates a sample engineering schematic for installingdata acquisition equipment and EPMS hardware at a site.

Appendix IV shows a sample vendor order for ordering data acquisitionequipment and EPMS hardware for installation at a site.

DETAILED DESCRIPTION

Prior to a detailed description of the disclosure, the followingdefinitions are provided as an aid to understanding the subject matterand terminology of aspects of the present systems and methods, areexemplary, and not necessarily limiting of the aspects of the systemsand methods, which are expressed in the claims. Whether or not a term iscapitalized is not considered definitive or limiting of the meaning of aterm. As used in this document, a capitalized term shall have the samemeaning as an uncapitalized term, unless the context of the usagespecifically indicates that a more restrictive meaning for thecapitalized term is intended. A capitalized term within the glossaryusually indicates that the capitalized term has a separate definitionwithin the glossary. However, the capitalization or lack thereof withinthe remainder of this document is not intended to be necessarilylimiting unless the context clearly indicates that such limitation isintended.

DEFINITIONS/GLOSSARY

ATS operational information (or data): information or data related to anATS or collected from an ATS. Generally includes emergency poweravailable status, emergency breaker closed status, normal poweravailable status, normal breaker closed status, normal powermeasurement, emergency power measurement, load power measurement,voltage for each ATS phase, current for each ATS phase, total current,rated current, percent rated current, power factor, frequency, percenttotal generator capacity, and any other similar measurements as willoccur to one of ordinary skill in the art.

Automatic Transfer Switch (ATS): item of industrial equipment thatenables automatic transfer back and forth from utility power toemergency power (i.e. generator-supplied power) as needed.

Automatic load test (ALT): a test of one or more items of EPSS equipmentthat is initiated remotely via a terminal display or user interface inwhich the selected EPSS equipment to be tested is used to actually powera portion of a facility during the test.

Automatic no load test (ANLT): a test of one or more items of EPSSequipment that is initiated remotely via a terminal display or userinterface in which the selected EPSS equipment to be tested does notactually power any portion of a facility during the test. Generally,only generators are tested during an automatic no load test.

Data acquisition equipment: equipment used to collect operational datafrom EPSS equipment. Generally includes monitoring sensors (such asthermocouples, resistive temperature detectors (RTDs), pressure senders,current transformers (CTs), and limit switches), connectors required byparticular types of monitoring sensors, power supplies, fuel gauges andother gauges, power meters, status indicators, video cameras,microphones, vibration sensors, inertial sensors, motion sensors,actuation components, solenoids, and relays, but may also include anyother equipment as will occur to one of ordinary skill in the art. Someitems of EPSS equipment require installation of data acquisitionequipment, whereas other items of EPSS equipment are manufactured toinclude some or all of the required data acquisition equipmentcomponents.

Emergency event: a sudden or unexpected loss in utility power causing aneed for generation of emergency power.

Emergency power: power supplied by an EPSS, and more specifically, agenerator. Generally synonymous with backup power or generator power.

Emergency Power Management System (EPMS): a system constructed asdescribed in this document, that enables managing, controlling, andtesting of a plurality of items of EPSS equipment at one or morefacilities.

Emergency Power Supply System (EPSS): system capable of supplyingemergency power to a facility when normal or utility power fails or isunavailable. An EPSS generally includes at least one generator, at leastone ATS, and at least one fuel supply, but may also include switchgear,a fuel management system, and other related equipment. Some EPSS's maycomprise only ATS's. Generally synonymous with power system.

Enterprise server: a computer server as commonly understood in the art.Enterprise server includes all of the functionality of the site server,but with added functionality of hosting a web-based graphical userinterface (GUI) or display for user interaction. Also provides rollup ofmultiple sites.

EPMS hardware: components used to install data acquisition equipment onor around items of EPSS equipment and connect the data acquisitionequipment to one or more interface modules and the management computersystem. Generally includes mounting racks, mounting hardware, andcommunication links (such as cables, fiber optics, wiring, and wirelessequipment), but may also include any other hardware necessary tointegrate and operate a functioning EPMS.

EPSS operational information (or data): includes both ATS operationalinformation and generator operational information.

Facility: a place at which an EPMS is installed and made operative. Forexample, a facility may include a hospital, university, airport, or someother similar site, or may be a subset of such a site, such as acafeteria, main building, small plane hangar, etc. Generally synonymouswith site.

Fuel supply: an individual fuel tank, or fuel line to a larger tank, orsome other source of fuel used to power a generator in an EPSS.Generally synonymous with fuel tank.

Generator: generally includes an engine (mechanical power source) and anelectrical generator that are capable of generating power when usedtogether. Generally synonymous with genset.

Generator operational information (or data): information or data relatedto a generator or collected from a generator. Generally includes jacketwater temperature, exhaust temperature, oil pressure, coolanttemperature, battery charging voltage, battery charging current, enginerunning status, engine “not in auto” status, high water temperaturealarm(s), low oil pressure alarm(s), engine speed, engine overspeedalarm(s), engine overcrank alarm(s), engine running time, percentgenerator capacity, power, rated load, voltage for each phase, currentfor each phase, frequency, and any other similar measurements as willoccur to one having ordinary skill in the art.

Intelligent EPSS equipment: items of EPSS equipment that aremanufactured or preconfigured to include some or all of the necessarydata acquisition equipment to provide operational data to the managementcomputer system. Intelligent EPSS equipment generally requires little orno retrofitting and installation of data acquisition equipment, and alsomay include a control panel or controller for delivering EPSSoperational information directly to an interface module.

Interface module (IM): intelligent device capable of receiving EPSSoperational data from data acquisition equipment or control panels atitems of EPSS equipment, normalizing and organizing that data, andtransmitting the data to the management computer system for furtherprocessing and display. An interface module may comprise a remoteterminal unit (RTU), programmable logic controller (PLC), or othersimilar intelligent device embedded with software capable of performingnormalization and transmission functions of EPSS operationalinformation.

Load: generally refers to the power consumed by a circuit. As usedherein, a load includes the power consumed by equipment at a facility,as well as the power required to operate the facility itself.

Location: the physical place where one or more items of EPSS equipmentare located. A location may include a room in a building, or thebuilding itself, or an area in or around a building, or some othersimilar place as will occur to one of ordinary skill. Generally, an EPSSmay be in one location or spread amongst several locations, but,alternatively, a location will generally not include more than one EPSS.

Management computer system: the combination of servers, networks,terminals, databases, proprietary management software, and other relateditems used to generate and operate an EPMS for a given facility.

Manual load test (MLT): a test of one or more items of EPSS equipmentthat is initiated physically at the specific items of EPSS equipment tobe tested in which the selected EPSS equipment is used to actually powera portion of a facility during the test.

Manual no load test (MNLT): a test of one or more items of EPSSequipment that is initiated physically at the specific items of EPSSequipment to be tested in which the selected EPSS equipment does notactually power any portion of a facility during the test. Generally,only generators are tested during a manual no load test.

Power disruption event: an event that causes a loss of utility powerand, generally, an activation of emergency power. Generally includesemergencies and other unplanned utility power losses, as well as EPSSequipment tests.

Region: a particular section of the country, such as a state, country,or other similar area.

Site: Generally synonymous with facility.

Site server: server that is generally located at a site or facility, andis responsible for interfacing with all interface modules at the site aswell as any other auxiliary equipment. Site server also managesinter-process communications at the EPSS level between individual itemsof EPSS equipment for test and emergency coordination and management.Generally, site servers collect and log data from EPSS equipment andtransmit that data to an enterprise server for further processing.

Site survey tool: a tablet computer, laptop computer, personal digitalassistant (PDA), or other similar device used to collect informationrelated to items of EPSS equipment at a given site and upload thatinformation to a management computer system.

Switchgear: generally refers to the combination of electricaldisconnects, fuses, and/or circuit breakers used to isolate and manageelectrical distribution equipment.

Terminal display: computer interface used to view and control EPSSequipment and data related to same via a management computer system.Generally synonymous with interface, user interface, or graphical userinterface (GUI).

Utility power: power supplied by a traditional utility power grid.Generally synonymous with normal power.

Overview

For the purpose of promoting an understanding of the principles of thepresent disclosure, reference will now be made to the embodimentsillustrated in the drawings and specific language will be used todescribe the same. It will, nevertheless, be understood that nolimitation of the scope of the disclosure is thereby intended; anyalterations and further modifications of the described or illustratedembodiments, and any further applications of the principles of thedisclosure as illustrated therein are contemplated as would normallyoccur to one skilled in the art to which the disclosure relates.

Aspects of the present disclosure generally relate to systems andmethods for managing and monitoring a plurality of emergency powersupply systems (EPSS's) in virtually real time via an emergency powermanagement system (EPMS). Additional aspects relate to easily andefficiently creating and installing an EPMS at a facility to carry outthe managing, monitoring, and testing functions of the EPSS equipment atthe facility. Further aspects of the disclosure are directed toproviding predictive analyses and operational information related to theEPSS equipment. Also, aspects of the present disclosure relate tonormalizing EPSS equipment information across varying vendors, makes,and models of equipment so as to provide a unified view of all equipmentacross a given facility.

Referring now to the figures, FIG. 1 illustrates an overview of anembodiment of an emergency power management system (EPMS) 10. As shown,utility power is delivered by power lines 15, or some other similarmechanism, to various facilities. The facilities may be ports 20,airports 22, or hospitals 24, as shown, but may also be any facilitythat requires or uses emergency power supply systems (EPSS's), such asuniversities, military bases, government structures, communicationsservice installations, data processing centers, office buildings,scientific laboratories, sewage pumping stations, retail outlets,residential complexes, and other similar facilities. Most of the time, afacility is powered by utility power. Some of the time, however, utilitypower is lost due to inclement weather 30, planned blackouts,malfunctions at a sub-station, or many other reasons. In thesesituations, the facility's EPSS's take over and generate the powerneeded to effectively operate the facility.

FIG. 1 shows a sample of a plurality of EPSS's for the hospital 24.While only the hospital's 24 EPSS's are demonstrated, it will beunderstood that the other facilities' EPSS's will be similar to thehospital's, and that each facility may include one or more EPSS's.Typically, each EPSS will include at least one automatic transfer switch(ATS) 160, at least one generator 165, and at least one fuel supply 32.Some EPSS's, however, will include multiple ATS's 160, generators 165,and fuel supplies 32, and will additionally include switchgear 34, fuelmanagement systems, and other equipment. Other EPSS's may include onlyATS's 160, and no generators 165. As will be understood by one havingordinary skill in the art, switchgear 34 is generally used in an EPSSsetting when two or more generators 165 are involved to aid in theeffective transfer of power. Additionally, as will also be understood,the fuel supply 32 within any EPSS may be an individual fuel tank, or aconnection to a larger, facility-wide fuel tank, or a combinationthereof.

In the embodiment of the EPMS 10 shown in FIG. 1, interface modules 40are installed at the EPSS's to collect, process, normalize, and transmitEPSS operational data to the server(s) 105 for further processing. Theinterface modules 40 receive EPSS operational information from dataacquisition equipment that is either retrofitted onto the EPSS equipmentor is pre-installed on the equipment by the manufacturer. The dataacquisition equipment generally includes monitoring sensors, powermeters, vibration sensors, temperature readers, alarm/status contactsensors, and other similar equipment capable of collecting EPSSoperational information from the items of EPSS equipment andtransmitting that information to the interface modules 40. For thegenerators 165, the generator operational information may include theoil pressure of the engine, the battery voltage, the engine runningstatus, the exhaust water temperature, and many other measurements aswill occur to those skilled in the art. The ATS operational informationmay include a reading as to whether emergency power is available (i.e.whether the generator 165 is ready and capable of supplying neededpower), a reading as to whether normal or utility power is available,whether the normal power breaker is closed, and many other measurementsas will occur to those skilled in the art.

Further, each EPSS may include only one interface module 40, or multipleinterface modules depending on the desires of the system user or on thenumber of items of EPSS equipment in a given EPSS. In some embodiments,each interface module 40 is capable of interfacing with a plurality ofitems of EPSS equipment, but more than one interface module may beincluded in a given EPSS based on the quantity and physical location ofthe EPSS equipment. Generally, the interface modules 40 includemicroprocessors capable of receiving and processing the EPSS operationalinformation. Additionally, in some embodiments, the microprocessorswithin the interface modules 40 normalize the incoming EPSS operationaldata into unified data outputs for subsequent processing. Thisnormalization is accomplished by passing the incoming EPSS operationalinformation through predefined algorithms based on the specificmanufacturer and model of the item of EPSS equipment from which theinformation is being received (discussed in greater detail below).

After the EPSS operational information is processed by the interfacemodules 40, the information is delivered via network 115 to server(s)105, where it is stored on database(s) 110, and further processed andmade available for viewing at local terminal 45 or remote terminal(s)47. The combination of server(s) 105, database(s) 110, network(s) 115,and terminal(s) 45, 47, as well as proprietary management software andother related items, serve to comprise one embodiment of the managementcomputer system 60. The management computer system 60 is used, accordingto one embodiment, to initiate and subsequently operate an EPMS 10. Aswill be understood, while only one local terminal 45 and two remoteterminals 47 are shown in FIG. 1, many more terminals may be used withinembodiments of the present systems and methods. Further, the EPSSinformation is processed into tables, graphs, charts, and otherpresentation forms to enable a user to view the processed EPSSinformation at a terminal 45, 47 through an interactive display 50. Inone embodiment, the interactive display 50 may also include videos andaudio associated with the EPSS equipment, which are captured by cameras195 installed around the EPSS equipment. Further embodiments of theinteractive display 50 include interactive maps detailing locations andstatus of EPSS equipment throughout a facility, one-line diagramsillustrating connections between EPSS equipment and utility or emergencypower, reports based on EPSS operational information generated overtime, and various other displays and features.

Through the interactive display 50, a system user may not only view andanalyze EPSS operational information being generated by the EPSSequipment, but may also initiate and monitor tests of the equipmentremotely. In this way, testing parameters and specifics may be enteredby a user at a terminal 45, 47, transmitted either through a network 115or directly to a server 105, and then further transmitted to theinterface modules 40, which then command the generators, ATS's, andother items of EPSS equipment to startup and operate accordingly. Whilea test is occurring, the interface modules 40 receive EPSS operationalinformation from the equipment that is subject to the test, and transmitthis information back to the server(s) 105 for processing. The EPSSinformation that is recorded and processed during a test can then beused to generate reports, either for purposes of compliance or simplyfor the facility's own benefit.

As shown in FIG. 1, the network(s) 115 may be data networks, intranets,the interne, or any other similar networks capable of transmittinginformation. Additionally, as shown, all facilities may be connected toa centralized server 105 or servers via a network 115. In this way, alocalized user of the EPMS 10 for a given facility may be able to manageand control the EPSS equipment associated with his or her facility, butmay not be able to view or interact with EPSS equipment at a separatefacility. An overall system operator, however, may be able to monitorall EPSS equipment from all facilities through a secured network 115.Also, rather than operating through a network, a local facility user canview EPSS operational information through an interface 55 connecteddirectly to one or more interface modules 40 at the facility. Thisinterface 55 may be a terminal 45, or it may comprise some alternateviewing mechanism, such as a wireless device (for example, and embeddedWindows® machine). Accordingly, a system user may view, manage, andmonitor all of the EPSS equipment at a given facility through aninterface 55, a local terminal 45, or a remote terminal 47.

The materials discussed above in association with FIG. 1 merely providean overview of an embodiment of the present system for managingemergency power supply system equipment, and are not intended to limitin any way the scope of the present disclosure. Accordingly, furtherembodiments of the systems and methods and more detailed discussionsthereof will be described below.

First Embodiments

Generally, one form of the present disclosure is a system formonitoring, managing, and testing a power system having local generatorsand connections to the utility power grid. Turning to FIG. 2, a system100 is shown with a server 105 and storage 110 connected to data network115. Server 105 in this embodiment includes processor 120, memory 125,network interface 130, input interface 135, and output interface 140, asshown in FIG. 3 and as will be understood by those skilled in the art.Power, ground, clock, and other signals and circuitry are omitted forclarity, but will be understood and easily implemented by those skilledin the art.

With continuing reference to FIG. 3, network interface 130 in thisembodiment connects server 105 to network 115 for communication of databetween server 105 and other devices attached to network 115. Inputinterface 135 manages communication between processor 120 and one ormore push-buttons, UARTs, IR and/or RF receivers or transceivers,decoders, or other devices, as well as traditional keyboard and mousedevices. Output interface 140 provides a video signal to display 145,and may provide signals to one or more additional output devices such asLEDs, LCDs, or audio output devices, or a combination of these and otheroutput devices and techniques as will occur to those skilled in the art.

Processor 120 in some embodiments is a microcontroller or generalpurpose microprocessor that reads its program from memory 125. Processor120 may be comprised of one or more components configured as a singleunit. Alternatively, when of a multi-component form, processor 120 mayhave one or more components located remotely relative to the others. Oneor more components of processor 120 may be of the electronic varietyincluding digital circuitry, analog circuitry, or both. In oneembodiment, processor 120 is of a conventional, integrated circuitmicroprocessor arrangement, such as one or more PENTIUM 4 or XEONprocessors from INTEL Corporation of 2200 Mission College Boulevard,Santa Clara, Calif. 95052, USA, or ATHLON XP or OPTERON processors fromAdvanced Micro Devices, One AMD Place, Sunnyvale, Calif. 94088, USA. Inalternative embodiments, one or more application-specific integratedcircuits (ASICs), general-purpose microprocessors, programmable logicarrays, or other devices may be used alone or in combination as willoccur to those skilled in the art.

Likewise, memory 125 in various embodiments includes one or more typessuch as solid-state electronic memory, magnetic memory, or opticalmemory, just to name a few. By way of non-limiting example, memory 125can include solid-state electronic Random Access Memory (RAM),Sequentially Accessible Memory (SAM) (such as the First-In, First-Out(FIFO) variety or the Last-In, First-Out (LIFO) variety), ProgrammableRead-Only Memory (PROM), Electrically Programmable Read-Only Memory(EPROM), or Electrically Erasable Programmable Read-Only Memory(EEPROM); an optical disc memory (such as a recordable, rewritable, orread-only DVD or CD-ROM); a magnetically encoded hard drive, floppydisk, tape, or cartridge media; or a combination of these memory types.Also, memory 125 is volatile, nonvolatile, or a hybrid combination ofvolatile and nonvolatile varieties.

Returning to FIG. 2, utility power line 150 provides power to load 155via Automatic Transfer Switch (ATS) 160. When utility power deliveredthrough line 150 is unstable or insufficient, ATS 160 manages a partialor total switchover to power generated by generator 165 and deliveredthrough line 170. In various embodiments, ATS 160 is an automatictransfer switch manufactured by ASCO, Russelectric, APC (such as itsRack ATS product), Cummins (such as its POWER COMMAND transferswitches), BayTech (such as its ATS Series Transfer Switch), GE Zenith,or Caterpillar, just to name a few options. Similarly, generator 165 isselected, in various embodiments, from the Caterpillar 3500 family,Cummins generator sets, and other models which will occur to thoseskilled in the art. In some instances, generator 165 and ATS 160 areintegrated in a single unit, while in others the units are distinct.

In various embodiments, generator 165 includes a built-in interface 175,which may be used in its factory configuration or supplemented withadditional interface hardware and/or software to provide the interfaceused by system 100. In other embodiments, generator 165 includes only alimited number of built-in sensors (or none at all), and interface 175must provide all or substantially all of the instrumentation for thatgenerator 165. In some embodiments, generator 165 is connected to gensetinterface module 175, which collects operational parameters fromgenerator 165 and makes them available to other devices via network 115.In various embodiments, the parameters provided by genset interfacemodule 175 includes the genset's fuel level, oil pressure, “running”status, water temperature, exhaust temperature, output frequency, enginespeed, applied torque, DC output voltage, and running time meter, justto name a few.

ATS interface module 180 detects the state of ATS 160 and makes thatinformation available via network 115 to other devices connected to thenetwork. The data made available by ATS interface module 180 includes,in various embodiments, its running status, input level, overridestatus, voltage, current, power output, power factor, and the like. Insome embodiments, some or all of these variables are captured and madeavailable via network 115 by one or more power meters (not shown)connected to or near the ATS.

Sensors 185 and 190 detect the state of supply lines 170 and 150,respectively, on the generator and utility inputs, respectively, to ATS160. This data is also provided via network 115 to other devices thatare connected to network 115. Camera 195 captures images of generator165 over time so that devices connected to network 115 can captureand/or display still pictures or motion video of the physical site ofgenerator 165 at desired times. In various embodiments, multiple camerasprovide images in a variety of views and/or spectra as necessary ordesired. Terminal 199 is also in communication with network 115 and isconfigured to monitor and/or control other devices on network 115.

Further, in various embodiments, multiple transfer switches 160,generators 165, sensors 185, 190, cameras 195, and interface modules175, 180 are in communication with network 115 to implement andinstrument a system that meets the power needs of a building,organization, institution, or group. Multiple terminals 199 communicatewith server 105 to access data compiled or calculated there, orcommunicate with other devices and interfaces to read operationalparameters or control those devices.

Server 105 collects data produced by interface modules 175 and 180,sensors 185 and 190, and camera 195, storing some or all of that data instorage unit 110. The data may be stored using any technique that wouldoccur to one skilled in the art, including but not limited to, storingall such data, sampling the data at various intervals for longer-termstorage, implementing circular buffers and snapshots, and otherstrategies. Server 105 also calculates aggregate information, such asuptime and running time for a device, maxima and minima of operationalparameters over time, and the like, and constructs graphical depictionsof captured data either on a scheduled, “snapshot” basis or on demand.Terminal 199 accesses the data on server 105 and (through server 105) instorage 110 so that an individual at terminal 199 can monitor and/orcontrol ATS 160, generator 165, and/or other controllable devices usingthat information. In various embodiments, server 105 makes this dataavailable in various forms, such as via FTP, HTTP, automaticallygenerated email, or the like. In some embodiments, the data provided toterminal 199 is substantially real-time information, while in othersserved data is drawn from a snapshot of the relevant device(s), while instill others some data of each type is available.

FIG. 4 shows a system 200 that includes multiple subsystems 201 a, 201b, 201 c, and 201 d. Each subsystem roughly resembles system 100 asshown in FIG. 2 and discussed in relation thereto, though the varioussubsystems may be in a single geographical location or multiplelocations, could include the same or different numbers of generators165, ATS units 160, sensors 185, 190, cameras 195, and other components,and may include elements that are the same or different in make, model,and/or configuration from those in other subsystems. Server 203 collectsoperational parameter information from a server 105 from each subsystem201 a, 201 b, 201 c, and 201 d, compiles that information, and saves itin storage 205. Enterprise server 203 also calculates aggregate data andgenerates graphical displays for showing on monitor 207 and/or terminal209.

Communication between subsystems 201, server 203, and terminal 209occurs via one or more networks 208. In various embodiments, network 208(and network 115 in FIG. 2) comprises one or more local area networks(LANs), wide area networks (WANs), virtual private networks (VPNs),dedicated communication circuits, device-level (e.g., Modbus) networks,and the like. One or more routers, switches, subnetworks, bridges, andthe Internet may appear in networks 115 or 208, or between two or moreportions of systems 100 and 200, as will occur to those skilled in theart.

Software implementing functionality at server 105 (see FIG. 2) in oneembodiment is shown in a block diagram in FIG. 5. In this embodiment, amemory 125 (see FIG. 3) is encoded with programming instructionsexecutable by a processor 120 (again, see FIG. 3) to implement softwaresystem 202, which includes user interface layer 210, service layer 220,and data layer 250. User interface layer 210 manages user interactionswith other parts of the software system 202, including communication ofinformation captured by the system to one or more users. Service layer220 manages the business logic and data flow in the system, while datalayer 250 manages storage of captured data and configuration informationfor various system elements and in various repositories.

In this embodiment, user interface layer 210 includes ASP.NET clientcomponent 212, which provides a variety of user-interface resources aswill be understood in the art. OPC web control component 214 provideshuman-machine interface (HMI) components to ASP.NET client 212 forAJAX-style presentation of data and capture of user control events.Webcam interface 216 accepts a stream of images from a camera 195 (seeFIG. 2) and provides data to ASP.NET client 212 for display as needed.Each of the components in user interface layer 210 is associated with acommon security identity 218 in its interaction with components inservice layer 220 and data layer 250.

Service layer 220 comprises several elements that manage data flow andimplement business logic in the system. Control manager 222 detects andexecutes logging events, starts and stops locally connected controllableentities, starts and manages the system configuration state, managementof software licensing, and detection of alarm events for notifications(by e-mail, for example). Control manager 222 communicates with ASP.NETclient 212, which interacts with the state manager 224, tag manager 226,and sequencer 228 to implement a state machine that controls operationof the server, maintains session states, and provides new states basedon input and programmed transitions. Tag manager 226 maintains arepository of information about the tags that are available to managedevices through the underlying OPC client 232, and loads the relevanttag configuration information at system startup, including configurationand device data, data logging configuration, and alarm loggingconfiguration. Meanwhile sequencer 228 manages automated testing ofdevices according to schedules and commands executed by the system.

These four components 222, 224, 226, and 228 share security identity 230in their interaction with ASP.NET client 212, OPC client 232 and filestorage 252. OPC client 232 accesses data via Modbus TCP OPC server 234(or any other similar industry standard device protocol converted to OPCcompliant format), which in this embodiment captures data from network115 via I/O block 254. In this embodiment, OPC server 234 is publishedby Kepware (www.kepware.com), though any industry standards-compliant orother suitable OPC server may be used. OPC (“OLE for Process Control,” aDistributed Common Object Model (DOOM) technology) client 232 and OPCserver 234 share security identity 236 in their interaction with OPC webcontrols component 214, tag manager component 226, logger 238, and I/Osubsystem 254.

Logger component 238 maintains data captured via OPC client 232 indatabase 256 using techniques that will occur to those skilled in theart. In some embodiments, logger component 238 also stores softwareevents, queries issued, data pulley and capture events, and the like.Logger 238 has its own security identity 240 to authenticate and in someembodiments encrypt some or all of these interactions with OPC client232 and database 256.

Similarly, alarm manager 242 monitors the stream(s) of data that flowthrough OPC client 232, checking them against limits defined by thesystem and/or users as discussed elsewhere herein. When such limits areexceeded, predetermined acts are taken, such as recording the event indatabase 256, raising alerts in the user interface via ASP.NET client212, sending email or pages, or raising visible and/or audible alarms,to name just a few possibilities. Alarm manager 242 also has its ownsecurity identity 244 to authenticate and secure its interactions, asappropriate, with OPC client 232, ASP.NET client 212, and database 256.

Data layer 250 in this embodiment comprises file storage element(s) 252,I/O controllers and devices 254, and database 256. File storage 252comprises one or more elements as described above in relation to storageelement 110 of FIG. 2, and provides read/write storage for variouselements of the system, including ASP.NET client 212, tag manager 226and sequencer 228. As will be understood by those skilled in the art,file storage 252 can be monolithic or distributed, homogeneous orheterogeneous, or have parts of each type as needed or desired for aparticular system.

Input/output block 254 provides the interface between server 105 andnetwork 115, so that data streams can be captured and devices on network115 can be controlled, and data can be shared with web-based terminalsand enterprise-level servers. In various embodiments, I/O interface 254comprises one or more network interface cards (NICs); Modbus interfacehardware; other standard, custom, or proprietary data interfaces, orsome combination thereof.

Database block 256 conceptually represents one or more databases, whichcould take on any of many forms that will occur to those skilled in theart. As some examples, database 256 may comprise one or more logicaldatabases, may be monolithic or distributed, may be housed in volatilememory, nonvolatile hard drives, or optical media, and may be of therelational, object-relational, flat, hierarchical, network,object-oriented, semistructured, associative, entity-attribute-value, orcontext models, to name several examples. In fact, database 256 in someembodiments is hosted on server 105 and stored in storage 110 (see FIG.2), though in other embodiments the host and/or storage is locatedelsewhere, or in a combination of local and remote locations.

In various embodiments, the “security identities” described hereinprovide distinct entities for control and monitoring of data access. Forexample, these identities in some embodiments are used to limit dataavailable to software entities bearing particular identities,authenticate transfers of data between software entities, and/or providepublic-key encryption keys for encrypted transfer of data betweenentities. Other applications of security identities in the context ofthis description will occur to those skilled in the art.

Turning to FIG. 6, system 300 comprises user interface layer 310,service layer 320, and data layer 350. In many respects, implementationsdescribed in relation to software system 202 may also be applied tosoftware system 300, though in some embodiments it is particularlyadapted to operate as a meta-server in the system configuration shown inFIG. 4. In this embodiment, user interface layer 310 includes ASP.NETclient 312 for presentation of information to users and capture of userinput, and OPC web controls 314 for providing an interface between thedata provided through OPC client 332 and the presentation layer ofASP.NET client 312. Webcam interface 316 collects and processes datafrom one or more cameras 195 (see FIG. 2) for presentation throughASP.NET client 312. The three components of user interface layer 310share security identity 318 in their interaction with other componentsof software system 300.

Service layer 320 comprises configuration loader/sequencer 328, OPCclient 332, logger 338, and alarm manager 342. Logger 338 and alarmmanager 342 operate similarly to the corresponding elements 238 and 242,respectively, of FIG. 5, though they have access to and process datafrom multiple sites and systems 201. Because they have access to morecomplete sets of data, they can provide a more complete picture of theactivities in system 200 including, for example, the effects of aregional power outage on a multi-site institution or the status andresults of multi-site testing (organized through this system orotherwise). Alarm manager 342 can be configured to take one or morealarm actions based on data from any site 201 in system 200, or evenbased on data from multiple sites that is captured substantiallysimultaneously or over time.

OPC client 332 connects to servers 105 in systems 100 at each sitesystem 201 to collect data from those systems. Configurationloader/sequencer 328 manages electronic files in file storage 352.Configuration loader/sequencer 328, in one example, loads from storage352 a file that describes the hierarchy of devices in network 200,including generators, interfaces, cameras, sensors, ATSs, terminals,servers, and the like as organized into locations, areas, and regions.The file preferably has a human-readable, structured format (such as XMLor a variant thereof) for ease in creating, reading, and processing suchfiles. Configuration loader/sequencer 328 also reads from file storage352 a file that outlines one or more tests that are to be run on thesystem, as is discussed in more detail herein.

In the embodiment of system 300 illustrated in FIG. 6, each of thecomponents of service layer 320 (configuration loader/sequencer 328, OPCclient 332, logger 338, and alarm manager 342) has its own securityidentity 330, 336, 340, and 344, respectively, for secure interactionswith user interface layer 310 through its security identity 318. Thisapproach has the advantage of fairly granular control over (and loggingof) access to data by the components of service layer 320. Inalternative embodiments, a common security identity for those componentsmakes authentication and local inter-process communication more simple,while making granular access control more challenging.

Data layer 350 includes file storage 352 and database 356 for storingand providing access to configuration and data in system 300. Each ofthese components may have one or more subcomponents as discussed abovein relation to file storage 252 and database 256. In various embodimentsfile storage 252 and 352 use the same hardware and storage strategy,while in other embodiments the storage approaches are different.Likewise, database 256 and database 356 may have the same or differentcharacteristics, hardware, software, and topology.

In normal operation, servers 105 and 210 (see FIGS. 2 and 4,respectively) provide access via data networks 115 and 215,respectively, to a browser-based interface. As described herein, server105 provides access to data from a particular physical site, whileserver 210 provides access to data from multiple sites. In either case,the present embodiment uses a tab-like bar 410 (as shown in FIG. 7) toprovide access to users to sections of the interface such as a “LiveView” of the system; “Testing” configuration, status, and resources;“Reporting” of stored data “Alarms” configuration and history; and“Administration” (“Admin”) of the system.

Referring to FIG. 7, in a “Live View,” all or part of a hierarchy 415organizes generator resources. In this embodiment, a region 412 has oneor more areas 414, and each area 414 has one or more locations 416,which in turn are each associated with one or more entities 418. At eachlevel in hierarchy 415, the interface provides a background image withcustomizable indicators that show the positions of elements in the nextlevel.

In various embodiments, the background image is a map (political,topographical, or other kind), a schematic, a one-line drawing, oranother image uploaded by an administrator or user. Using configurationfile(s) or an administrative interface, one is able to select abackground image for each level and/or item in hierarchy 415, and toplace on each image selected overlay text, icons, or other images thatindicate the relative position of resources on the next lower level inthe hierarchy within the displayed branch or element. In some levels ofthe display in some embodiments, the graphic and/or text that isdisplayed to indicate the position of the lower-level branch or elementis adapted in color, shape, or content to show the status of that item.For example, text, dots, or borders around text or icons might be greenwhen the unit is operating normally, yellow if alarms have beentriggered, red if utility power is not available, and blue if a test isrunning at a given site or on a given device. Of course, other colorschemes, icons, or indicators for use in this system will occur to thoseskilled in the art.

In various embodiments, background image 420 is established by a systemdesigner, uploaded by an administrator, selected by a user, or otherwiseexists on server 105/210. A user or system designer places indicators422 and 424 on background image 420 to illustrate the approximateposition of those items on the image (such as location on a map, orcircuit-wise position in a schematic diagram). In some embodiments,users can move indicators 422 and 424 by dragging and dropping them intodifferent positions on background image 420. In some embodiments, itemsbelow indicators 422 and 424 appear as part of the indicator itself(here, “One-Line 1” and “One-Line 2” appear as part of indicator 422because they are entity-level items in the hierarchy at the “Main”location). In some embodiments users are presented with the option ofchanging the font, size, and color of indicator text, and in othersusers are provided the facility to choose what aspects of status orcriteria are indicated by one or more available indication techniques asdescribed above.

In some embodiments, some view levels show live operational data, suchas frequency, voltage, uptime, and the like, as part of indicators 422and 424. The system in this illustrated embodiment maintains a databaseof common makes and models of equipment and sensors so that when asystem is being set up or new equipment is added to the existing system,a system architect can easily add all relevant information for eachdevice by selecting a device model, assigning a text label to the newdevice, placing it in the hierarchy, and selecting operationalparameters and the display mode for real-time data. The database ofdevices automatically provides the device-specific tags that can be usedin a query to retrieve particular parameters (when a pull-type model isused) or to parse messages when a push-model is implemented. Thedatabase in this embodiment also provides standard limits for at leastsome of the device's operational parameters so that users can simplyswitch alarms “on” and have rational limits instantly in place. Ofcourse, when a device in a system is not in the database, a systemarchitect, administrator, or operator can add the relevant informationconcerning its available tags and standard operating conditions (or evenjust those tags and/or data points to be used) to integrate the newdevice type into the system.

FIG. 8 illustrates an entity-level display according to one embodiment.Display 450 includes tab-bar 410 and hierarchy display 415, but the bulkof display 450 is taken up with information specific to a particularentity. Live data section 451 shows the current status and recent eventhistory for the items selected in hierarchical display 415. Current datafor the selected device is shown in current data display region 453,images of the selected device (individual captured images or a livevideo feed) are shown in image display region 455, and an event historyfor the selected device is shown in event display region 457.

The parameters shown in current data display region 453 may be selectedfrom available data tags for the selected device based on the device tagdatabase described herein by an administrator or user, depending on theneeds and preferences of the system designer. Likewise, in someembodiments, the events shown in event display region 457 may includeall events generated for the selected device, may include only aparticular type of event (such as testing events, startup and shutdownevents, and the like), and/or may be filtered by severity or recency ofthe event, as will be understood by those skilled in the art. In otherembodiments, no filtering is available.

In the center of display 450 is image display region 455, which isadapted to display for users one or more images of the generator 165and/or ATS 160 at that site as captured by one or more cameras 195. Invarious embodiments this image display region 455 shows still images,time-lapse photography, and/or video (real-time or for selectedperiods). Any or all of these regions 453, 455, 457, in variousembodiments, include navigation and interface manipulation features forpaging, moving, resiting, filtering, layering, and the like as will alsooccur to those skilled in the art.

Control/test status display region 461 of the present embodimentdisplays whether the device is operating or not in display widget 463,as well as whether any tests are active for the entity in the teststatus display region 465. Alarms relating to the displayed entity areshown in alarm display region 471. This region 471 includes a table 473of alarm events that shows, for each alarm event, zero or more rows 475,each with the date and time of an alarm event, a text description of thealarm, a type or level of the alarm, and the tag value that triggeredthe alarm. Other columns in the table may show other information inaddition to or instead of this collection of information as will occurto those skilled in the art. Further, alarm display region 471 and/oralarm data table 473 in various embodiments also includes facilities tosort and filter alarm information based on user preference oradministrator selection.

A feature of some embodiments of the present system is a facility thatenables users to script tests for one or more entities in the system, toschedule or manually initiate those tests, to monitor the tests inprogress, and to review the results of the tests. In some embodiments,each test is a sequence of digital assertions to be made to a controldevice that controls an entity in the power system, paired with anapplicable status query that is made to the same control device forverification that the assertion was properly received and is beingprocessed. The system collects parameters identified in the test scriptfor reporting as well as real-time display while the test is inprogress. The system provides user interface components that enableusers to monitor a test in progress, pause the test, resume the test, orabort the test as necessary or desired based on the data being collectedor other factors.

FIG. 9 illustrates test setup/scripting interface 500, which includestest naming and selection region 510, test sequencing region 520, andSave and Cancel buttons 530 and 540, respectively. Test naming andselection block 510 includes a drop-down list 512 which is populatedwith named tests that have been created in the system. Users selectexisting tests with drop-down list 512, change the name of an existingtest using test box 514, create a new test with button 516, an delete anexisting test using delete button 518.

Tests are scripted using test scripting interface 520. When a new testis created using New Test button 516, the Test Steps list box 522 isemptied to make a place for display of the scripting steps. The useractivates New Test Step button 524 to create a new step in the script,which the user then configures using interface elements 526. Interfaceelements 526 in this embodiment allow a user to specify a descriptionfor the test step, the site server that will execute the step, theentity on which the step is executed, the duration of the step, and thelogging group (see further discussion below) that should apply to datacaptured during the test step. Either when the test is scripted or whenit is executed, tag manager 226 (see FIG. 5) is consulted to determinewhich tag should be asserted to initiate the test. If a user wishes todelete a step, the user selects the step in list box 522, then clicksDelete Test Step button 528. The step is then removed from the internalrepresentation of the test, and the step's entry in Test Steps list box522 is removed.

When the test is scripted as the user desires, he or she activates SaveConfiguration button 530, and the test configuration is committed tonon-volatile memory. Typically tests will be stored at enterprise server210 so that test steps for devices at multiple sites can be coordinated.In alternative embodiments, tests or test steps are stored at one ormore site servers 105. In either event, operational data aboutelectrical generators 165 and other equipment in subsystems 100 arecollected and reported by site servers 105 to enterprise servers 210 forpresentation to users, storage in the historical record, and as afactual resource for reporting.

FIG. 10 illustrates test schedule/status interface 550, which includesactive test status display region 555 and test schedule display region560. Active test status display region 555 shows a list of test scriptscurrently active, including an identifier for the test, a briefdescription of the test, the date and time at which the test wasstarted, the elapsed time since the test started, the step number withinthe script that is currently being processed, the execution status ofthe test (active, paused, aborted, completed, and the like), the entitybeing tested, and other information additional to or instead of thisinformation as will occur to those skilled in the art. Test scheduledisplay region 560 in this embodiment includes a selector for existingtest schedules in existing schedule display element 562, test controlwidgets 568 in test control display region 564, and a history of testsconducted under the selected schedule in test history region 566. Inother embodiments, the display of existing schedules, control facilitiesfor starting, pausing, resuming, and stopping tests, test statusdisplays and histories are separated and/or combined on multipleinterface screens, or have alternative display configurations as willoccur to those skilled in the art.

One such possible alternative display is shown in FIG. 11. Test schedulecalendar display 570 includes active test status list 572, which isanalogous to active test status display region 555 in FIG. 10. Inaddition, calendar display 570 includes test scheduling calendar 574that shows test names and times in a calendar view for easy evaluationand navigation by users. Weekly and annual calendars may also bedisplayed as will occur to those skilled in the art. When a test scripthas been defined (see, for example, the discussion relating to FIG. 9),it can be added to test scheduling calendar 574 using a context menu,pop-up dialog, or the like.

FIG. 12 shows an example test report for an exemplary test in thisembodiment. Test report 579 includes a title, an identification of theentity or entities tested, the date and time at which the test wasinitiated, and data captured during the test. The parameters beingcaptured, as discussed above, may be selected by the test designer oradministrator from measurable parameters for that entity (which thesystem knows based on the entity database described herein). Samplefrequencies for captured data in this embodiment are determined when thetest is designed, though in some embodiments the sampling frequency andtiming are also adjustable on-the-fly, and may vary over time as willoccur to those skilled in the art.

Because the data captured (both during normal operation and duringtesting) is stored in a standard database in this embodiment, reportdesign software may be used to create reports for the system withoutmuch difficulty. For example, CRYSTAL REPORTS, published by BusinessObjects, 3330 Orchard Parkway, San Jose, Calif. 95134, USA, may be usedto generate desired human-readable or machine-readable reports as willbe understood by those skilled in the art. Alternatively, MicrosoftReport Builder may be used to construct reports using these dataresources as desired or needed. Report configurations and/or outputs maybe stored on a site server 105 or enterprise server 210, or both, orelsewhere as will occur to those skilled in the art.

An example reporting/history interface is shown in display 600 in FIG.13. Display 600 includes display criteria selectors in parameterselection display region 610. In this embodiment, users select theserver(s) and logging group(s) to be accessed for data that will bedisplayed, dates and times defining the range of interest, roll-up andsummary options, and output styles and forms for the report or graph.Available tags are listed in and may be selected using tag selectiondisplay region 620, and the system provides output with the selectedparameters in output display region 630. Many alternative parameterselection techniques and output techniques are used in variousembodiments as will occur to those skilled in the art.

Alarm management interface 650 is shown in FIG. 14. This interface 650is updated in real time using AJAX or other display/interface techniquesthat will occur to those skilled in the art. The alarm interface 650 inthis embodiment shows the dates and times of recent alarms, textassociated with the alarms, the tags and limits that triggered thealarms, as well as the alarm types and the tag values when the alarmswere triggered. This data is displayed in table 655, which in someembodiments the user can manipulate to sort and filter as desired. FIG.15 shows a display 660 of historical alarms. Display 660 includesselection display region 662 and data/navigation display region 665,though other arrangements and interface techniques will occur to thoseskilled in the art.

FIG. 16 illustrates a data logging configuration interface 670 in thisfifth embodiment. A server in the system is selected in server selectionregion 672, and a “logging group” is selected or created in logginggroup selection region 674. The logging group is named and enabled ingeneral configuration region 676, which also can be used to determinethe logging type, set the sample rate, and select whether toautomatically remove data beyond a certain age.

For event-type logging groups, the window of time in which data iscaptured and saved before and after the event, as well as the parametersfor reporting the event are selected in event configuration displayregion 678. The example display 670 shows parameters for reporting in anemail and/or saving in a data file when the event is triggered, thoughother reporting techniques may easily be used without undueexperimentation by those skilled in the art.

Database logging for the logging group is configured in database loggingdisplay region 680. In this interface section the user can enable ordisable database logging, provide the connector provider, server,database and table names, and other configuration information forestablishment of database connections, and enter other parameters aswill occur to those skilled in the art.

Event triggers for the logging group are selected using event triggerdisplay region 682, which provides a list of available event triggersand a facility for the user to select one or more of them to triggerevents for the logging group. Likewise, tags to be included in thelog(event, database, or otherwise) for the logging group are selected inlogging tag selection region 684. The user can select a different serverfrom which tags to be selected with selection widget 686, though otherselection techniques may be used as will occur to those skilled in theart. When the parameters for the logging group have been set or modifiedas desired, a “Submit” or “Commit” button (not shown) may be activated,and the updated configuration is stored in the system.

In alternative embodiments, different software architectures may beused, such as different layering delineations, object encapsulations,and security identity groupings. In some alternatives, processes shownin this disclosure as a single software system (such as FIG. 5 or FIG.6) are distributed among multiple processors in a homogeneous orheterogeneous distributed system.

Configuration of Embodiments of EPMS

One aspect of the present system includes the efficient installation andconfiguration of an emergency power management system (EPMS) 10 at afacility. FIG. 17 shows an overhead view of an example facilityincluding multiple emergency power supply systems (EPSS's). The facilityshown in FIG. 17 is a hospital 1705. The hospital building 1705 includesthree primary rooms—an operating room 1710, a dialysis center 1715, andan MRI room 1720. In the embodiment shown, each of the three rooms has aseparate EPSS that supplies power to that room in the event of anemergency or loss of utility power. As shown, EPSS 1, which suppliespower to the operating room 1710, includes three ATS's 160, switchgear34, two generators 165, and a fuel supply 32. EPSS 2, which suppliespower to the dialysis center 1715, includes two ATS's 160, one generator165, and one fuel supply 32. EPSS 3, which supplies power to the MRIroom 1720, includes only one ATS 160, one generator 165, and one fuelsupply 32. As will be understood, these representations of various EPSSconfigurations are presented for illustrative purposes only, and variousother configurations are possible. Additionally, although the hospital1705 shown includes only one building with three separate EPSS's, itwill be understood that many facilities will include several buildingswith many EPSS's.

FIG. 18 illustrates one embodiment of the steps involved in the systemdesign automation 1800 for creating and installing an EPMS 10 at afacility or site, such as the hospital 1705 shown in FIG. 17. Generally,system design automation 1800 involves collecting information related toEPSS equipment at a given facility, processing that information, andautomatically generating via a management computer system 60 therequired bill of materials, vendor orders, work orders, engineeringschematics, and any other items needed to make operative an EPMS 10 atthe facility. In the embodiment shown, at step 1805, a site survey isconducted to electronically capture information related to the items ofEPSS equipment at the site. This information may be collected via a sitesurvey tool, such as a laptop computer, personal digital assistant(PDA), tablet computer, or other similar capture mechanism.Additionally, as will be understood by one having ordinary skill in theart, the EPSS equipment information may also simply be written on paper,and subsequently entered into the management computer system 60 forfurther processing.

FIG. 19A illustrates a sample display 1905 of a site survey tool usedfor collecting generator 165 information according to one embodiment ofthe present system. As shown, the site survey display 1905 includesthree categorical tabs—a general tab 1910, an electrical tab 1912, and afuel tab 1914. When the general tab 1910 is selected, generalinformation relating to the specific site is entered, such as the nameof the site, the site contact information, and other similarinformation. When the fuel tab 1914 is selected, information relating toa given fuel supply 32 or fuel supplies for the site's EPSS's isentered, such as a name for the fuel supply, which generators 165 aresupplied by the fuel supply, and other similar information. In display1905, the electrical tab 1912 is shown as selected, in which informationrelating to a site's generators 165 and ATS's 160 is entered.

Display 1905 shows a sample screen for entering generator 165information for a given EPSS into a site survey tool. Located on theleft side of the display 1905 is a hierarchy 1910 for listing andnavigating through sites, locations, and specific items of EPSSequipment. As shown, a user may select to add a new site or system viathe “Add Site” 1916 or “Add System” 1918 features, add a new locationthrough the “Add Location” 1920 feature, or add new generators 165and/or ATS's 160 via the “Add ATS” 1922 and “Add Gen” 1924 features. Asshown in hierarchy 1910, “ATS1,” “ATS2,” “ATS3,” and “ATS4” have alreadybeen entered into the system under “Location1,” and “ATS5,” “ATS6,”“ATS7,” and “ATS8” have been entered under “Location2.” Currently,“Gen1” is highlighted in hierarchy 1910, which designates that the userhas selected the “Add Gen” 1924 feature, and is adding a generator 165entitled “Gen1” to the selected EPSS (“EPSS1”).

Located on the right side of display 1905 is generator information entryregion 1915. Within information entry region 1915 are several fieldsthat may be either directly filled in by a user, or include drop-downmenus from which specific items may be selected. As a user surveys theEPSS equipment at a given site, that information is entered into a sitesurvey tool utilizing an interface such as display 1905, and thatinformation is uploaded to the management computer system 60 for furtherprocessing. The embodiment of information entry region 1915 shown inFIG. 19A includes “Generator Name” region 1930, “Panel Location” region1932, and “Generator Outside?” selection region 1934. As will beunderstood, a user may designate whatever name the user desires for eachgenerator 165, ATS 160, etc. As shown, the generator name given to theparticular generator at issue is “Gen1.” Thus, all information enteredinto information entry region 1915 pertains to Gen1.

Further, the “Panel Location” region 1932 relates to the specificposition where a control panel (if any) for the generator 165 will bemounted. For example, the generator 165 may be located outside of abuilding, but the user may wish to install the control panel inside ofthe building to protect it from inclement weather. Accordingly, the userwould indicate this information in the “Panel Location” region 1932.Also, the “Generator Outside?” region 1934 is selected if the chosengenerator 165 is physically located outside.

Generator information entry region 1915 further includes manufacturerinformation region 1940, in which the manufacturer, model, and serialnumber for the engine (mechanical power source) and electrical generatorassociated with a particular generator 165 are entered. Thismanufacturer, model, and serial number information is used later by themanagement computer system 60 to tailor the EPMS 10 for a facility tothe specific equipment at the facility. In rated values region 1945, therated current, voltage, kilowatts (power), and revolutions per minute(RPM) for the generator 165 are entered. As will be understood, thevalues entered into rated values region 1945 may be entered in anystandard measurements, such as volts, amps, etc., depending on thedesires of the user. The fuel type and horsepower for the particulargenerator 165 are also entered into “Fuel Type” region 1950 and“HorsePower (hp)” region 1952 respectively. “Year Installed” region 1954denotes in what year the generator at issue was installed at thefacility. The “Fuel Tanks” region 1956 generally includes a list ofavailable fuel tanks or fuel supplies 32 capable of supplying fuel tothe generator 165. In one embodiment, all fuel supplies 32 that areactually associated with the generator 165 are highlighted in the “FuelTanks” region 1956.

Further, “Exhaust” region 1960 enables a user to identify whether theparticular generator 165 has dual ports, and if so, what size probes arerequired for measuring exhaust outputs from the generator. “Controller”region 1965 allows a user to designate a controller or control panel, ifone exists (control panel discussed in greater detail below). As shown,CT region 1970 allows a user to input required sizes and ratios forcurrent transformers (CTs) for the specific generator 165 that may beneeded to operate the EPMS 10. Moreover, “Comments” region 1975 and“Special Instructions” region 1978 permit a user to enter any additionalinformation pertaining to the item of EPSS equipment being surveyed thatis not covered by the other fields in information entry region 1915.Also, buttons 1980 allow a user to save, delete, or copy the informationrecorded in information entry region 1915.

Turning to FIG. 19B, a display 1906 is shown of a sample site surveytool used for collecting ATS 160 information according to one embodimentof the present system. The display 1906 includes many of the samefeatures and fields as are included in the generator display shown inFIG. 19A, although the fields are modified so as to capture ATS-relatedinformation. FIG. 19B includes the hierarchy 1910 and an ATS informationentry region 1982. As shown, “ATS1” is highlighted in hierarchy 1910,and thus the information contained in information entry region 1982pertains to “ATS1”. As will be understood by one having ordinary skillin the art, within embodiments of the present disclosure, theinformation entered in the site survey tool may be edited and changedlater if it is discovered that information was entered incorrectly, orif a particular piece of EPSS equipment is modified, or for any otherreason.

Information entry region 1982 includes fields in which the name andpanel location of an ATS 160 may be entered, similarly to a generator165 as shown in FIG. 19A. Entry region 1982 also includes manufacturerinformation region 1984 for recording the manufacturer, model, andserial number of the ATS 160 at issue. The rated values (current,voltage, power supply, etc.) may also be entered into the informationentry region 1982 via rated values region 1986. “Transition” region1988, “Service” region 1990, and “Style” region 1992 are all fields inwhich specific attributes of the ATS 160 are entered for subsequentreporting purposes.

Additionally, ATS display 1906 includes entry fields for recordingcontroller information and CT information as it relates to theparticular ATS 160, similarly to the generator survey display 1905.Entry region 1982 further includes a check box 1994 for denoting whethervoltage monitoring of the ATS is needed for available signals. Also, asis the case with generator entry region 1982, specific commentspertaining to the particular ATS 160 being surveyed may be entered into“Comments” region 1996.

As will be understood by one of ordinary skill in the art, theinformation collection fields and regions depicted in FIGS. 19A-B arepresented for illustrative purposes only, and are not intended to limitthe information collected pertaining to generators 165 and ATS's 160 forvarying EPSS's. In some embodiments, more information may be required,whereas in other embodiments, less specific information will be neededto effectively configure an EPMS 10.

Referring again to FIG. 18, once all the EPSS equipment information hasbeen entered into the site survey tool (step 1805), the information isstored on the site survey tool in a flat file or by other similarstorage mechanism (step 1810), and then uploaded to the managementcomputer system 60 via an interactive portal (step 1815). In someembodiments, rather than collecting EPSS information for a facility viaa site survey tool, a facility employee may enter and upload EPSSequipment information for his or her facility directly to the managementcomputer system portal (step 1820). Thus, a facility can actively manageand edit its EPSS equipment information without using a site surveyorand site survey tool. Regardless of how information is uploaded to themanagement computer system 60, the information is subsequently processedand stored in a database of facility information (step 1825). Dependingon the embodiment, the database of facility information may includeinformation pertaining only to a particular site or facility, or mayinclude information relating to multiple sites and facilities.

In some embodiments of the present system, after the EPSS equipmentinformation has been initially processed and stored in a database (step1825), this information may be viewed by a user through a facilityportal 1830. The user may be an employee or officer of the facility, andmay wish simply to utilize the facility portal 1830 to keep track ofEPSS equipment inventory and specifics related to the EPSS equipment atthe facility. For example, a particular facility may have accumulatedhundreds of items of EPSS equipment over a span of many years, and theemployees of the facility in charge of maintaining the EPSS equipmentmay not have an accurate, comprehensive inventory list of all equipmentat the facility. Or, a facility operator may simply wish to have aneasily accessible electronic inventory of all EPSS equipment at thefacility. In some cases, the facility operators may be totally unawareof certain items of EPSS equipment, and locations of that equipment, atthe facility. Thus, a comprehensive inventory list of all EPSS equipmentat a site or facility may be helpful.

Additionally, the ability to view all items of EPSS equipment at afacility via a facility portal 1830 enables the facility to perform“load control” during an emergency. For example, in a severe ice storm,hurricane, or other natural disaster, a facility may be operating onemergency power supplied by its EPSS's for an extended period of time.In these extreme circumstances, fuel consumption may need to be closelymonitored and conserved, especially when new fuel shipments may beunavailable. Accordingly, by viewing all EPSS equipment through thefacility portal 1830, and determining what facility rooms and equipmentare powered by each item of EPSS equipment, the facility employees canmake an informed decision to shut down certain, non-critical generators165 to conserve fuel, and allow only the critical circuits to continuereceiving emergency power. As will be understood, many other beneficialuses will follow from use of the facility portal 1830.

FIG. 20 shows a sample display 2000 for a facility portal 1830 accordingto one embodiment of the present system. The display 2000 includes aninventory report generation field 2005, in which a user can generate aprinted report of particular EPSS equipment for a given site (discussedin greater detail below). As shown, the display 2000 also includes a“Site List” 2010 detailing all sites available for viewing by theparticular user. Also shown is a “System Summary” field 2015 for theparticular selected site. In the embodiment shown, the “System Summary”field 2015 provides a brief list of the EPSS equipment located at thesite. For example, the system summary 2015 in FIG. 20 shows that the“Main Hospital” site has three switches (ATS's 160) rated at 2,230 Amps,one generator 165 rated at 1,000 kW, and one fuel tank (with currentlyzero gallons contained therein). Thus, the “System Summary” field 2015allows a user to cohesively view, at a high level, the total amount ofEPSS equipment, and corresponding potential power output, for a givenfacility.

Also shown in display 2000 is an “Entities” field 2020 that lists eachindividual item of EPSS equipment at the given facility. In FIG. 20,“ATS-EA” is shown as selected, and the corresponding details related to“ATS-EA” are displayed in the “Entity Detail” field 2025. In theembodiment shown, the “Entity Detail” field 2025 presents theinformation that was entered during the electronic capture of the EPSSequipment information (step 1805) for the particular item of equipmentselected. Accordingly, the name, rated current, voltage, manufacturer,model, style, and other information relating to the selected ATS isshown. The display 2000 also includes a “Panels” section 2030 forlisting the electrical breaker panel(s) associated with the item of EPSSequipment selected. The “Panels” section 2030 further includes circuitbreaker information for circuit breakers contained within the given“Panel”, including the name and current rating of the circuit breaker.By using the facility portal display 2000, a system user can quickly andeasily access any information relating to EPSS equipment at a givensite.

As mentioned, the embodiment of the display 2000 shown in FIG. 20includes an inventory report generation field 2005. This field enables auser to generate reports for EPSS equipment contained at a site. Thesereports may be used by a facility as comprehensive analyses of theequipment contained at the facility. These reports may also be useful tovendors and manufacturers of EPSS equipment. The vendors andmanufacturers may use this information to determine which facilities areusing their equipment, how much of the equipment is being used, whichfacilities likely need new equipment, and various other uses as will beapparent to one of ordinary skill.

FIG. 21A shows a sample generator inventory report 2101 created by anembodiment of the inventory report generation field 2005 contained indisplay 2000. The generator inventory report 2101 includes a “GeneratorName/Location” field 2105 that lists each generator 165 at the facilityby its name (as entered into the site survey tool during step 1805), andthe physical location of that generator. The generator inventory report2101 also includes a “Generator Details” section 2110, as well as a“Fuel System Details” section 2115 corresponding to each listedgenerator 165. In the embodiment shown, the “Generator Details” sectionlists the information pertaining to each generator 165 that wascollected during the site survey (step 1805), such as the generatormanufacturer, model, horsepower, etc. The “Fuel System Details” section2115 shows the fuel type and estimated consumption rate for each listedgenerator 165. As will be understood, the generator inventory report2105 may show more or less information related to the selectedgenerators 165 than what is shown in FIG. 21A. As will also beunderstood, although the sample generator inventory report 2101 includesfive generators 165, many more than five or as few as one may beincluded in the report 2101.

FIG. 21B is a sample ATS inventory report 2102 created by an embodimentof the inventory report generation field 2005 contained in display 2000.Much like the generator inventory report 2101, the ATS inventory report2102 lists specific ATS's 160 included within a facility, as well asdetails associated with those ATS's. The fuel tank inventory report2103, shown in FIG. 21C, lists the fuel tanks for the given facility,the capacity of each tank, and comments related to the specific tank(such as the manufacturer, model, etc.). As shown, the fuel tankinventory report 2103 also includes a “Generators Serviced” field 2130,which shows the site, the system (EPSS), and the name of the generator165 served by each respective fuel tank. As will be understood by one ofskill in the art, varying amounts of information, as well as varyingnumbers of ATS's 160 and fuel tanks, may be included in embodiments ofATS inventory report 2102 and the fuel tank inventory report 2103.

Further, embodiments of the inventory report generation field 2005 mayalso generate manufacturer reports 2201, 2202 relating to the items ofEPSS equipment at a given site. FIG. 22A illustrates a sample ATSmanufacturer report 2201 for a particular facility or site. The ATSmanufacturer report 2201 lists the ATS's 160 located within the site bymanufacturer 2205. Also, within each manufacturer 2205 breakdown, thespecific model 2210 of each ATS 160 is listed, as well as the number ofoccurrences of that particular model at the facility. The generatormanufacturer report 2202 shown in FIG. 22B follows the same format asthe ATS manufacturer report 2201, only for generators 165 instead ofATS's 160 at the facility. As will be understood, the reports 2201, 2202may comprise any format and any level of information desired by theuser, and are not limited to the specific formats and amounts ofinformation shown in FIGS. 22A-B.

Referring again to the embodiment of the system design automation 1800shown in FIG. 18, after the EPSS equipment information has beenprocessed and stored in a database (step 1825), the information isfurther processed according to a proprietary rules engine to generatethe bill of materials, engineering schematics, and other items necessaryto install and operate an EPMS 10 for a given facility (step 1835).Generally, a rules engine is a software system that helps manage andautomate certain predefined rules within a business or system. In oneembodiment of the present system, the rules engine software is part ofthe management computer system 60, and includes predefined algorithmsand commands that generate the bill of materials, work instructions, andother outputs that are specifically tailored to each site to create acustomized EPMS 10 for the site.

In one embodiment, all of the major recognized manufacturers and modelsof EPSS equipment are stored in the management computer system 60, aswell as the required data acquisition equipment and EPMS hardware neededto integrate each model of equipment into a functioning EPMS 10. Thus,when a specific manufacturer and model of a particular generator 165 orATS 160 is captured via the site survey tool (step 1805), andsubsequently uploaded and processed (steps 1810-1835), the managementcomputer system 60 recognizes that particular model of equipment fromits database and generates a list of the EPMS hardware and dataacquisition equipment needed to incorporate that particular model ofequipment into a functioning EPMS 10. Accordingly, for each differentmodel of EPSS equipment, different data acquisition equipment, EPMShardware, work instructions, and other elements may be required tointegrate each item of EPSS equipment into an overall EPMS 10. Further,as will be understood by one of ordinary skill, if a particular model ofEPSS equipment is not already stored in the management computer system60 (for example, as new models of equipment are unveiled), a systemoperator can simply upload the parameters of the specific model ofequipment such that the system 60 will recognize that model of equipmentand will also store it for future configurations.

By way of example, assume a “Model Y” generator 165 made by “Company X”is one of many different generators 165 located at a facility. Alsoassume that, based on research and manufacturer specifications, a “ModelY” generator 165 made by “Company X” requires the installation of dataacquisition equipment including one fuel gauge, one power meter, onevibration sensor, and two monitoring sensors on the generator in orderto gather all necessary information needed for adequate monitoring andmanaging of the generator via an EPMS 10. Further assume that someadditional EPMS hardware components are needed, such as fiber opticcables and wiring, to connect the data acquisition equipment to aninterface module 40. Additionally, assume that a “Model Z” generator 165made by “Corporation W” is another generator at the facility. However,for purposes of this example, assume the “Model Z” generator 165 made by“Corporation W” is an “intelligent” generator, and it is preconfiguredby the manufacture to include all necessary sensors, gauges, and otherdata acquisition equipment needed to monitor its informationalparameters. Thus, as the two models of generators 165 are processed bythe system design automation 1800 component, the rules engine softwarewill generate a list of required parts (i.e. one fuel gauge, one powermeter, one vibration sensor, and two monitoring sensors, as well as acertain length of fiber optic cables and wiring) for the “Model Y”generator. However, the software will recognize that the “Model Z”generator does not require the retrofitting of any data acquisitionequipment, and thus may only generate a list of minor EPMS hardwareneeded, such as connection wiring to connect the already-existingsensors on the generator control panel to an interface module 40.

As shown in FIG. 18, the rules engine software creates a bill ofmaterials detailing the data acquisition equipment and EPMS hardwarerequired to integrate all items of EPSS equipment at a facility into afunctioning EPMS 10 (step 1840). A sample bill of materials is shown inAppendix I. In one embodiment, the bill of materials will include notonly the necessary data acquisition equipment and EPMS hardware, butwill include other items as well, such as site servers, interfacemodules 40, and other similar equipment. In another embodiment, the billof materials includes software licenses and terms of use for thefacility to use proprietary software associated with an EPMS 10.Further, the interface modules 40 needed for a given EPMS 10 are definedat step 1845 via the rules engine software based on the number andlocation of items of EPSS equipment at the facility.

As the bill of materials is generated (step 1840) and the interfacemodules 40 are defined (step 1845), order documents are also generatedfor installation of an EPMS 10 at the facility (step 1850). Generally,every facility or site will differ in terms of the equipment required tocreate an EPMS 10 at the site and to install and integrate thatequipment. For instance, the types and numbers of EPSS equipment aregenerally different at every site, the location of that equipment variesgreatly, and the way in which all of the EPSS equipment is connectedtogether and integrated with the management computer system 60 changesas a function of the differences in equipment and location. Thus, oneembodiment of the system design automation 1800 includes the generationof order documents, including a configuration file (step 1852), aproject template or plan (step 1854), electrical drawings and schematics(step 1856), work instructions (step 1858), and vendor orders (step1860). As will be understood, other order documents may be generated asneeded based on the requirements or desires of a system operator orfacility.

Additionally, as will be understood, all of the order documents (as wellas the bill of materials) are automatically generated by the rulesengine software based on the EPSS information collected during the sitesurvey (step 1805). This autogeneration or autoconfiguration enables thequick and efficient definition of all data acquisition equipment, EPMShardware, and other equipment needed to initiate an EPMS 10. Theautoconfiguration also enables creation of engineering drawings, workinstructions, and other items needed to initiate the EPMS 10.

Still referring to FIG. 18, the configuration file is generally an XML(extensible markup language) file or other similar file needed tointegrate the installed data acquisition equipment and EPMS hardwarewith the management computer system 60 to make operative an EPMS 10. Theconfiguration file minimizes the steps involved in setup andconfiguration of proprietary software onto a server at a facility. Theproject template is a plan that establishes suggested timelines, tasks,and other related items that will be necessary to complete the workinstructions and install all necessary equipment at a site. Accordingly,the project template interacts directly with the work instructions todetermine what tasks must be completed. Appendix II illustrates samplework instructions for installing the data acquisition equipment and EPMShardware at a site. Also generated are engineering schematics and/ordrawings detailing how various items of equipment should be connectedtogether and installed (step 1856). A sample engineering drawing isshown in Appendix III. Vendor orders are also created for ordering eachitem of data acquisition equipment and EPMS hardware from varyingmanufacturers (step 1860). A sample vendor order is shown in AppendixIV. In some embodiments, a vendor order system interfaces directly withan accounting system 1865 to track the cost and expense of items orderedfrom vendors, check available funds, and complete otheraccounting-related tasks.

Additionally, in one embodiment, a quote is generated detailing the costassociated with the installation of all data acquisition equipment, EPMShardware, and any other equipment (step 1870). Generally, the quoteaccounts for the cost of the equipment itself, as well as the laborassociated with installing the equipment, and any other miscellaneouscharges.

Once all of the order documents and the bill of materials have beengenerated (steps 1850 and 1840) and the interface modules 40 have beendefined (step 1845), the data acquisition equipment, EPMS hardware, andother necessary equipment are installed on or at the EPS S equipment atthe given facility, the configuration file is integrated into themanagement computer system, and an EPMS 10 for the facility is thus madeoperative.

Monitoring EPSS Equipment Via Configured EPMS

FIG. 23 is a diagram illustrating an embodiment of an installed andoperative EPMS 10 at the hospital facility 1705 previously shown in FIG.17. As shown, the data acquisition equipment and EPMS hardware have beeninstalled at the EPSS equipment and operatively connected to theinterface modules 40. As also shown, EPSS 1 includes three interfacemodules 40 for receiving EPSS operational information from the dataacquisition equipment, processing and normalizing that operationalinformation, and transmitting it to server(s) 105, 2305. Further, EPSS 2and EPSS 3 each include only one interface module 40. As will beunderstood, each EPSS may utilize varying numbers of interface modules40 depending on the number and location(s) of EPSS equipment included inthe specific EPSS. Additionally, video cameras 195 are shown asinstalled at each EPSS. These video cameras 195 provide video and audiofeeds of the EPSS equipment to the user terminals 45, 47. As will beunderstood by one of ordinary skill, while only one camera 195 is shownfor each EPSS, many more cameras are possible within embodiments of thepresent system.

As shown in FIG. 23, the interface modules 40 are connected to a network115 that provides communication between the modules and the server(s)105, 2305. As mentioned previously, a network 115 may comprise anintranet, internet, data network, or other similar network. The network115 enables the interface modules 40 to transmit EPSS operationalinformation to the server(s) 105, 2305 for further processing. Althoughthe embodiment of the EPMS 10 shown in FIG. 23 includes both anenterprise server 105 and a site server 2305, one of ordinary skill inthe art will understand that a site server is not necessary in allembodiments. The use of a site server 2305, or many site servers, incombination with an enterprise server 105 comprises a form ofdistributed computing. Generally, the site server 2305 is responsiblefor interfacing with the interface modules 40 and managing inter-processcommunications between items of EPSS equipment for tests of the EPSSequipment, emergency management, and other similar processes. The siteserver 2305 also collects and logs data from the EPSS equipment,provides alarms when certain predefined criteria are met, managestesting of the EPSS equipment, provides local visualization of the EPSSequipment, and other related functions.

The enterprise server 105, according to one embodiment, delivers all ofthe functionality of the site server 2305, with the added functionalityof rolling up all site servers to provide a global view of all EPSS'swithin a facility or many facilities. Use of an enterprise server 105allows for geographical distribution of the EPMS 10, such that if a siteserver 2305 malfunctions or becomes unavailable, the EPMS can continuefunctioning until the site server is repaired or replaced. Further,according to some embodiments, the enterprise server 105 provides ahosting of a web-based graphical user interface (GUI) 55 for userinteraction. The overall functions and processes of the site server(s)2305 and enterprise server(s) 105 will be described in more detailbelow. Additionally, as shown, the server(s) 105, 2305 interact withdatabases 110, 2310 to provide storage for incoming and processed data.

Still referring to FIG. 23, users of the EPMS 10 can access processedEPSS operational data via either local user terminal 45, or remote userterminal 47. Processed data is made available at terminals 45, 47 via anetwork 115. The terminals 45, 47 provide system users with aninteractive interface from which they can control, monitor, manage,view, and test the EPSS equipment at a given facility (as will bediscussed below in association with several interactive user displays).

In one embodiment of the EPMS 10, an interface 55 is connected directlyto an interface module 40 or modules, as shown in FIG. 23. In thisembodiment, the interface module 40 connected to the interface 55 has apublic IP address. The enterprise server 105 in this instance acts as ahosted site, and the public interface module 40 or modules tunneldirectly to the server. Generally, there is access control to thesection of the server 105 that is connected to the public interfacemodule(s) 40 such that only an authorized user associated with the givenfacility can access the EPSS equipment information through the hostedsite. This embodiment enables use of an EPMS 10 without installation andoperation of a site server 2305. Additionally, this embodiment tends toreduce costs associated with software licenses because the enterpriseserver 105 acts as a hosted site and spreads software costs amongst manyfacilities.

In many embodiments of the EPMS 10, user security limits access toEPSS's across varying facilities. In nearly all EPMS 10 interactions,user security determines which EPSS's the particular user may view,monitor, and control, and to what extent he or she may view, monitor,and control them. This user security is generally accomplished via ausername and password protocol, as will be understood in the art. Inthis way, an overall system operator may be able to manage many EPMS'sacross many facilities, for example, whereas an individual employee at agiven facility may only be able to view a portion of the EPSS's at theemployee's facility.

Referring now to FIG. 24A, a terminal display of a tabular site summaryview 2401 is shown for a sample site according to an embodiment of thepresent system. The site summary view 2401 is depicted under the “LiveView” tab 2420 of the terminal display, thus indicating a live, realtime view of EPSS equipment for the given facility. The site summaryview 2401 includes a hierarchy 2405 for listing and navigating throughsites 2410, EPSS's 2412, camera views 2414, and one-line views 2416 ofEPSS equipment. In other embodiments, as will be understood, thehierarchy 2405 may list other items as well, such as physical locationsof EPSS equipment, specific items of EPSS equipment, and other similarelements.

The tabular site summary view 2401 shown in FIG. 24A also includes asite summary display region 2425 that lists each EPSS for the selectedsite. As shown, the site “Clinic” 2410 is selected in the hierarchy2405, and thus the summary display region 2425 lists each EPSSassociated with the “Clinic” site. Within the summary display region, a“Top Level Summary” field 2430 displays all EPSS's for the site, and an“Alarm Summary” field 2460 lists any recent alarms associated with thesite. Turning first to the “Top Level Summary” field 2430, “Org Level”region 2432 simply lists the site associated with each EPSS shown in thefield 2430. The “System” region 2434 lists the name of each EPSSassociated with the selected site. In the embodiment shown, each EPSSname comprises a clickable link to a more detailed system view of thatparticular EPSS (discussed below).

The “Status” region 2436 in the “Top Level Summary” field 2430 indicatesthe overall status of each particular EPSS. As shown, all statuses areindicated as “READY”, designating that each EPSS is ready to beginoperating and supplying emergency power if needed. Other statusindicators may be displayed in “Status” region 2436 as well depending onthe actual status of the given EPSS, such as “RUNNING”, “MAINTENANCE”,and other similar statuses. For instance, a status of “RUNNING” mayindicate that at least one item of EPSS equipment in that particularEPSS is currently operating. A status of “MAINTENANCE” may indicate thatat least one item of equipment is currently undergoing maintenance work.As will be understood, other status indicators are possible withinembodiments of the present system.

Still referring to FIG. 24A, the “Since” region 2438 indicates at whattime and date each EPSS achieved its indicated status. The “Gen” region2440 and “ATS” region 2442 indicate, respectively, how many of the totalgenerators 165 and ATS's 160 in each EPSS are currently operating. The“Util kW” region 2444 shows the amount of utility power currently beingsupplied to certain loads that are also supplied by generator power. The“Gen kW” region 2446 indicates the amount of generator power beingsupplied to the same loads referred to in the “Util kW” region 2444.Further, the “% kW Rating” region 2448 shows what percentage of ratedgenerator power is currently being supplied by the generator(s) 165 ineach EPSS. Additionally, the “Fuel (Gal)” region 2450 indicates how muchfuel is available for each EPSS. As will be understood by one ofordinary skill in the art, other embodiments of the present system willinclude additional regions in the “Top Level Summary” field 2430indicating additional data related to the EPSS's listed in the field2430.

Referring now to the “Alarm Summary” field 2460 for the selected site,alarms associated with EPSS equipment at the site are shown. The alarmsare predefined by a system operator to notify a system user when acertain event occurs. For instance, an alarm may be generated when theRPMs of a generator 165 exceed a certain value, or when the exhausttemperature of a generator reaches a set value, or when an ATS 160malfunctions, or for any number of possible situations. In theembodiment of the “Alarm Summary” field 2460 shown in FIG. 24A,“DateTime” region 2462 indicates the date and time of the alarm, “Site”region 2464 indicates at which site the alarm occurred, and “System”region 2466 shows in which EPSS the alarm occurred. Further, “Entity”region 2468 specifies which item of EPSS equipment experienced thealarming condition. In “Alarm” region 2470, a brief narrative of thenature of the alarm is displayed. For example, the alarm shown in FIG.24A states that the water temperature of the noted generator 165 ishigh.

Additionally, “Type” region 2472 indicates what type of alarm occurred.For example, a designation of “hi” may indicate a moderately seriousalarming condition, whereas a designation of “hi hi” or “extremely hi”may indicate a very serious condition. Finally, under “Value” region2474, the specific value of the data parameter associated with the alarmis listed. In the example shown, because water temperature was indicatedin “Alarm” region 2470, the value of 78.69 shown in “Value” region 2474likely refers to the water temperature of the noted generator. As willbe understood, other indicators and data fields other than those shownin FIG. 24A may be employed to notify a system user that analarm-triggering event has occurred.

Referring now to FIG. 24B, a terminal display of a map site summary view2402 is shown for a sample site according to an embodiment of thepresent system. The site summary view 2402 shown in FIG. 24B correspondsto the same “Clinic” site shown in FIG. 24A, except that the map sitesummary view 2402 shown in FIG. 24B displays the EPSS's 2482 associatedwith the site in map form rather than tabular form. While the map sitesummary view 2402 shown in FIG. 24B provides less information about eachEPSS 2482 as compared to the tabular site summary view 2401, the mapview 2402 does provide a helpful geographical display of the locationsof each EPSS throughout the site.

Further, each EPSS 2482 shown in map view 2402 includes a status display2480 indicating the status of each EPSS, similarly to “Status” region2436 in the tabular summary view 2401. For example, a red status display2480 may indicate that at least one item of EPSS equipment in the givenEPSS 2482 is running, a blue status display may indicate that at leastone item of EPSS equipment is in maintenance mode, and a green statusdisplay may indicate that all items of EPSS equipment in the given EPSSare ready for operation. As will be understood, other status indicatorsare possible within embodiments of the present system.

Additionally, the embodiment of the map site summary view 2402 shown inFIG. 24B is interactive, such that a user may click (via a mouse orother selection tool) on each EPSS 2482 shown in the map view to drilldown to a more detailed EPSS view (discussed in detail below). Also, auser may click on the “ElectricalOneLine” link 2484 for each EPSS 2482to see a detailed one-line view of the particular EPSS (also discussedbelow).

Whether a system user is viewing a tabular site summary view 2401 or amap site summary view 2402, the user may interact with the terminaldisplay to view a more detailed view of a particular EPSS for theselected site. For example, if a user selects or clicks on EPSS “CR3” inthe “System” region 2434 of tabular site summary view 2401, then theuser will be directed to a tabular EPSS view 2501 of EPSS “CR3”, asshown in FIG. 25A. From the map site summary view 2402, a user mayselect EPSS “CR3” 2482 to view the same tabular EPSS view 2501 for“CR3”. Additionally, from either the tabular site summary view 2401 orthe map site summary view 2402, a user may simply click on “CR3” inhierarchy 2405 to be directed to the tabular EPSS view 2501 for “CR3”.

The embodiment of the tabular EPSS view 2501 shown in FIG. 25A includesboth a hierarchy 2405 and an EPSS display region 2510, wherein the EPSSdisplay region 2510 shows details and information related to the itemsof EPSS equipment contained in the selected EPSS. As shown, EPSS displayregion 2510 includes an EPSS status and testing field 2520, an “ATSSummary” field 2540, and a generator display field 2560. In oneembodiment, the EPSS status and testing field 2520 includes an alarmsection 2522 for indicating any alarms associated with the particularEPSS, and a system activity section 2524 noting any recent eventsassociated with the EPSS equipment. Generally, the system activitysection 2524 will display the date, time, and a brief description of themost recent event or events that have occurred in connection withequipment in the selected EPSS. An event may include a power disruptionevent, such as an emergency power loss or a test, or other events, suchas equipment maintenance, equipment malfunctions, and other similarevents.

The EPSS status and testing field 2520 further includes a statusindicator 2526 for displaying the current status of the EPSS equipment.As shown, the status of the selected EPSS is “READY”, indicating thatthe EPSS equipment is ready for operation. Also shown is a status clock2528 for showing the length of time that a certain status has beenongoing. For example, if the generator 165 associated with EPSS “CR3” iscurrently showing a status of “RUNNING”, then status clock 2528 wouldindicate the length of time the generator has been running.Additionally, status and testing field 2520 further includes testcontrols 2530, which are used to setup and initiate tests of the EPSSequipment contained in the selected EPSS. Testing of the EPSS equipmentwill be discussed in greater detail below.

Still referring to FIG. 25A, the “ATS Summary” field 2540 lists theATS's 160 associated with the selected EPSS. As shown, EPSS “CR3”includes four ATS's, the names of which are listed in “ATS” region 2542.In one embodiment, the listed ATS names are live, clickable links thatwill provide further details regarding a specific ATS when selected(discussed in more detail below). “Status” region 2544 shows the currentstatus of each ATS 160, and “Source” region 2546 indicates whether theATS is currently connected to “NORMAL” power (i.e. utility power) or“EMERGENCY” power (i.e. generator power). Additionally, normal powerregion 2548 indicates the actual voltage and current readings from thenormal power supply, whereas emergency power region 2550 indicates theactual voltage and current readings from the emergency power supply. Asshown, because all the ATS's 160 are connected to normal power, thevoltage and current readings shown in emergency power region 2550 arezero. Further, “% R Cap” region 2552 indicates the percentage of ratedload capacity currently being used, “kW” region 2554 shows the currentpower output being channeled through each ATS 160, and “% Load”indicates the percentage of maximum load connected to each ATS that iscurrently being powered by each ATS. As will be understood, other dataregions relating to ATS data may be included in “ATS Summary” field2540.

Referring now to generator display field 2560, a detailed display ofgenerator data for the generator 165 included in EPSS “CR3” is shown. Aswill be understood, if the selected EPSS includes more than onegenerator 165, then more than one generator display field 2560 would beshown in EPSS display region 2510. Alternatively, multiple generators165 may be listed in selectable tabular form, similar to the ATS's 160in “ATS Summary” field 2540. The generator display field 2560 includes amultimedia display 2562 for showing a live video and audio feed of theEPSS generator 165. The live video and audio feed shown in multimediadisplay 2562 is captured by camera 195 located at the physical locationof the generator 165. The multimedia display 2562 enables a system userto hear or see if there are any noticeable problems with the EPSSequipment. Also, if a system user wishes to initiate a remote test ofthe generator 165, the multimedia display 2562 shows whether someone isnear the EPSS equipment, such that the test can be aborted until theequipment is clear.

Also included in generator display field 2560 is electrical generatorregion 2564, which shows live data related to the electrical generatorin the genset for the selected EPSS. As shown, electrical generatorregion 2564 displays the present power output and frequency of theelectrical generator. Additionally, the electrical generator region 2564includes a percentage of rated power meter 2566, as well as percentageof rated power readings region 2568. In some applications, generatortesting must exceed 30% (or some other predefined value) of the ratedpower or load of the generator 165 to qualify as a valid test (discussedbelow). Thus, in some settings, it is advantageous to be able to view alive reading of the percentage of rated power being supplied by thegenerator 165.

Still referring to FIG. 25A, the generator display field 2560 furtherincludes an engine region 2570 for detailing live data related to theengine in the genset for the selected EPSS. As shown, engine region 2570displays the water temperature, oil pressure, and exhaust temperature ofthe engine. Engine region 2570 also shows the voltage and current of thebattery charger used in conjunction with the engine. Also displayed inthe embodiment of the engine region 2570 shown in FIG. 25A is an hourstotal 2572 showing the total hours that the particular engine hasoperated since it was manufactured. Further, “Main Fuel Tank” region2574 displays the volume of fuel available in the fuel supply 32 for thegiven generator.

As mentioned previously, the data displayed in EPSS display region 2510is collected from data acquisition equipment that was installed at or onthe EPSS equipment (or was preinstalled by the manufacturer) duringconfiguration of the EPMS 10. This data is normalized and transmitted(discussed below) through an interface module 40 or modules to themanagement computer system 60, and eventually displayed in virtuallyreal time via terminal displays, such as the tabular EPSS view 2501. Aswill be understood, the data collected and displayed in embodiments ofthe terminal displays may include more or less data than what isdisplayed in the tabular EPSS view 2501 and other views discussedherein.

Turning now to FIG. 25B, an embodiment of a sample one-line view 2502for a given EPSS is shown. The one-line view 2502 for a given EPSS maybe viewed by selecting “One-Line” in hierarchy 2405, or by clicking onthe “ElectricalOneLine” link 2484 in the map site summary view 2402.Generally, an embodiment of the one-line view 2502 displays liveconnections between utility power 2580 or emergency power 2582 for theloads 2584 supplied by an EPSS. Connection boxes 2586 represent ATS's160 and the switch position within the ATS's. In the example shown inFIG. 25B, all loads 2584 are shown as currently being supplied byutility power 2580. However, if a power disruption event occurs, and anyof the loads 2584 become supplied by emergency power 2582, the switchposition within connection boxes 2586 corresponding to those loads willautomatically switch and indicate that the load is being supplied byemergency power. Accordingly, the one-line view 2502 provides a viewingmechanism for monitoring the live connection status of various items ofEPSS equipment at a facility.

Referring again to FIG. 25A, if one of the ATS's 160 listed in “ATS”region 2542 is selected or clicked, a more detailed view of data relatedto that particular ATS will be displayed. FIG. 26 shows an entity detailview 2600 for a particular ATS 160 and particular generator 165 in agiven EPSS. The embodiment of the entity detail view 2600 shown issimilar to the tabular EPSS view 2501 shown in FIG. 25A, but with a moredetailed display of one of the ATS's listed in “ATS Summary” field 2540.As shown, the ATS named “ATS_(—)01E” has been selected, and live datacorresponding to “ATS_(—)01E” is shown in ATS detail region 2605.

According to one embodiment, the ATS detail region 2605 includes agraphical display 2610 indicating that the ATS 160 is connected tonormal or utility power. Normal connection indicator 2612 is highlightedto further demonstrate that the ATS 160 is connected to normal power,and normal available indicator 2614 is highlighted to show that utilitypower is in fact available. In the event of an emergency or other powerdisruption event, when normal power becomes unavailable, the ATS 160sends a signal to a generator 165 to begin running. Once the generator165 reaches the power output necessary to power the connected load, theemergency available indicator 2618 will become highlighted, the ATS 160will transfer the load to emergency power, and the graphical display2610 will indicate the switch to emergency power. Additionally,emergency connection indicator 2616 will become highlighted once theload has been connected to emergency power. Also included in theembodiment of ATS detail region 2605 shown in FIG. 26 is a maintenanceselector 2620 that enables a system user to place the selected ATS 160in maintenance mode.

In the embodiment shown in FIG. 26, on each side of indicators 2612 and2616 are ATS data regions 2630 and 2650 corresponding to normal powerdata and emergency power data, respectively. Each ATS data region 2630,2650 displays the amount of power and percentage of rated ATS currentchanneled through the particular ATS 160, as well as the percentage ofoverall rated EPSS power. Data regions 2630, 2650 also include voltageand current readings for each phase of a three-phase electric powertransmission through the ATS (i.e. A-B, B-C, C-A). As will be understoodby one of ordinary skill in the art, other collected values from ATS's160 within a site may be displayed in ATS detail region 2605 in additionto the values shown in FIG. 26.

A further terminal display contemplated within embodiments of thepresent system is a combined multimedia display 2700, as shown in FIG.27, for delivering live audio and video feeds for a plurality ofgenerators 165 and other EPSS equipment over a plurality of EPSS's at asite or facility. Generally, the combined multimedia display 2700includes a plurality of individual multimedia displays 2562 similar tothe generator display shown in FIG. 25A. The combined multimedia display2700 enables a system user to view many or all generators 165 or otheritems of EPSS equipment across a facility in one comprehensive view.

Still another terminal display contemplated within embodiments of thepresent system is an EPSS equipment roll-up view 2800, as shown in FIG.28, for listing all items of EPSS equipment at a given site. As shown,the “Comm's Status” tab 2805 is selected in the terminal display,indicating a view of the communication status between items of EPSSequipment and the overall management computer system 60. Generally, theequipment roll-up view 2800 lists all items of EPSS equipment at a givenfacility. When one or more items of EPSS equipment lose connection withthe management computer system 60, either due to a network outage, cutcommunication line, or for some other reason, the status indicator(s)2815 associated with those items of equipment will indicate a loss incommunication. In various embodiments, the indicators 2815 may indicatea connection loss via a flashing light, change in color, or some otheralerting mechanism.

In one aspect, the configured EPMS 10 provides predictive capabilities,such as predictive fuel consumption, performance of EPSS equipment overtime, average durations of power outages, seasons of the year when poweroutages are more frequent, and other similar predictive measures. By wayof example, FIG. 29 shows a terminal display of a fuel system summary2900 for a fuel tank that supplies EPSS equipment at a site. As shown,“Generator Summary” field 2905 lists all generators 165 currentlyoperating and drawing fuel from the noted fuel tank. As will beunderstood, while only one generator 165 is listed in the “GeneratorSummary” field 2905 in FIG. 29, many generators may be included if morethan one generator is actively drawing fuel from the fuel tank. Theinformation contained in “Generator Summary” field 2905 generallyincludes the specific generators 165 using fuel from the fuel tank, thesite and EPSS corresponding to each generator, the power being producedby each generator, the percentage of rated power being output by thegenerator, and any other data that the user desires related to thegenerator(s).

Still referring to FIG. 29, the “Tank Details” field 2910 displays dataassociated with the selected fuel tank. The “Name” region 2912 indicatesthe name given to the selected fuel tank during the site survey (step1805), and the “Status” region 1914 shows the status of the tank. Asshown, the status of the fuel tank is “ACTIVE”, indicating that fuel iscurrently being drawn from the tank. As will be understood, other statusindicators may be used as well, such as “READY”, “MAINTENANCE”, “EMPTY”,and other similar indicators. Generally, the “Tanks Details” field 2910also includes a “Level” region 2916 that shows the fuel level in thefuel tank (in gallons or some other similar measure). Also included is a“Capacity” region 2918 that displays the capacity of the fuel tank, aswell as a “% Full” region 2920 that shows what percentage of the fueltank is full. Additionally, “Generators” region 2922 lists thegenerators 165 supplied by the given fuel tank.

On the left side of the embodiment of the fuel system summary 2900 ispredictive fuel data field 2930. Generally, predictive fuel data field2930 includes a status indicator 2932, and a graphical representation ofthe fuel tank 2934 showing the fuel level currently contained in thetank. The actual fuel level is displayed in numerical form in “FuelLevel” region 2936. The consumption rate of fuel currently beingconsumed from the fuel tank is also displayed in “Consumption Rate”region 2938. In one embodiment, the consumption rate is determined byfuel sensors (i.e. data acquisition equipment) installed in the fuellines leading to the generators 165 at the facility that measure theconsumption rate of fuel when the generator is running. In anotherembodiment, the consumption rate is calculated by the managementcomputer system 60 based on the amount of fuel consumed by a generator165 when it is operating to supply power to a given load over a certaintime span. Thus, the management computer system 60 determines theaverage consumption rate for given loads for each generator 165 based onthe actual consumption data collected over time.

Once the consumption rate is determined, the total volume of the fueltank is divided by the consumption rate to determine the time left untilthe fuel tank will run out of fuel if all current generators 165continued to operate. This value is displayed in predictive fuel datafield 2930 in “Time To Empty* Running Gens” region 2940. The value shownin region 2940 is a prediction of how long the EPSS's connected to theparticular fuel tank can produce power at the current load if all of thecurrently-running generators continue to run, and no other generatorsbegin operating. As will be understood, this value 2940 will change inreal time as new generators 165 begin to run or already-runninggenerators stop running. In one embodiment, predictive fuel data field2930 also includes a measure of the time remaining until the fuel tankbecomes empty if all connected generators startup and begin operating toprovide power to the facility. This value is displayed in “Time ToEmpty* All Gens” region 2942. To calculate the value shown in region2942, the management computer system 60 calculates an average estimatedconsumption rate as if all generators were running based on loggedhistorical data of consumption rates for given loads for all generators165 at the facility. The total volume of the fuel tank is then dividedby the average estimated consumption rate of all generators 165 todetermine the time left until the fuel tank will run out of fuel if allfacility generators begin operating.

Using the predictive fuel capabilities described above, a facility canaccurately predict how long it can operate on emergency power, which maybe particularly helpful during emergencies, natural disasters, and thelike. Further, aspects of the present system provide other predictivecapabilities as well. For other predictive aspects, data is collectedand stored over time to provide information as to general trends andpatterns that would not be otherwise be known. For example, data may becollected as to what times of year are more likely to experience poweroutages (e.g. winter-time experiences more outages), such that afacility can replenish fuel tanks, provide routine maintenance, andother complete other tasks before these more frequent outage timesoccur. Or, historical data may reveal that power outages occur far morefrequently in the late afternoon, such that a facility can be more waryduring those times. Additionally, historical data may reveal that aparticular manufacturer or particular model of EPSS equipment is morelikely to fail or malfunction over time, and thus future ordering ofequipment can be tailored so as to avoid that equipment. As will beunderstood by one of ordinary skill, embodiments of the EPMS 10 may beused to collect and record a wide array of information from EPSSequipment that may be useful to a site or facility, and the informationcollected and predictive analyses performed are not limited to thosedescribed herein.

Interface Module

Generally, embodiments of the interface module 40 comprise intelligentdevices capable of receiving EPSS operational data from data acquisitionequipment or control panels at items of EPSS equipment, normalizing andorganizing that data, and transmitting the data to the managementcomputer system 60 for further processing and display. As described,embodiments of the EPMS 10 provide unified viewing, monitoring, testing,and other capabilities of a plurality of items of EPSS equipment ofvarying models manufactured by a plurality of manufacturers. Because ofthis variance in EPSS equipment, different signals and outputs are oftenreceived from the items of equipment. For example, some items of EPSSequipment may have been configured during the system design automation1800 with data acquisition equipment, whereas other items of equipmentmay comprise “intelligent” EPSS equipment that is manufactured toinclude all necessary sensing equipment. Thus, the intelligent equipmentmay be preconfigured to include a control panel (or “controller”) thatcollects EPSS operational information from the EPSS equipment andconverts that information into a different format than that produced bythe retrofit data acquisition equipment. Additionally, some equipmentmay provide data in different units (e.g. ° C. or ° F.) with differentvariances and tolerances. Accordingly, this varying EPSS informationshould be standardized and normalized by the interface module 40 ormodules to enable efficient, real time processing and display of theinformation to system users.

In one embodiment, an interface module 40 is a remote terminal unit(RTU), programmable logic controller (PLC), or other similar intelligentdevice embedded with software capable of performing normalization andtransmission functions of EPSS operational information. Generally, theinterface module 40 includes a microprocessor, program memory, and datamemory to carry out the processing functions of the embedded software.The interface module 40 also typically includes a communication bus(such as the ModBus® communications protocol) to provide communicationbetween the interface module and the servers 105, 2305 within themanagement computer system 60. Additionally, some embodiments of theinterface module 40 include a firewall for providing secured access toEPSS information as well as the EPSS equipment itself. Also physicallyincluded on the interface module 40 are sensor inputs and data outputsfor, respectively, receiving EPSS operational data from the EPSSequipment and transferring the processed data to the management computersystem 60. In additional embodiments, the interface module 40 mayinclude other components not described herein as will become apparent tothose of ordinary skill in the art.

Referring now to the processes of the interface module 40, FIG. 30A is aflow chart 3000 showing the basic functional operations of oneembodiment of the interface module for receiving, normalizing, andtransmitting EPSS operational data to the management computer system 60.At step 3005, the interface module 40 receives signals and data from oneor more items of EPSS equipment. As described, these signals may be invarying formats depending on the type of EPSS equipment from which theEPSS operational information is collected. The EPSS operational data maybe received directly from data acquisition equipment installed on theEPSS equipment during system design automation 1800, or from controlpanels connected to intelligent EPSS equipment, or directly from datasensors manufactured into the equipment, or from some otherinformational delivery source. Thus, the interface modules 40 shouldinclude functionality capable of connecting to and recognizing all ofthese disparate data sources.

At step 3010, the received EPSS operational data is normalized accordingto predefined parameters. Essentially, if raw operational data isnormalized to one standard format, set of units, etc., then subsequentprocessing and displaying of the data is made easier, faster, and moreefficient. Accordingly, it is beneficial for the management computersystem 60 to receive standardized generic generator data, orstandardized generic ATS data, for example, as opposed to varying typesof data from different makes and models of EPSS equipment. Thus, theinterface module 40 includes proprietary embedded software that performsnormalization functions. In one embodiment, configuration flags for eachspecific manufacturer and model of EPSS equipment are sent to theinterface module(s) 40 from the servers 105, 2305 such that theinterface module(s) can recognize the type of data they will receivefrom each piece of connected equipment. The configuration flags arepredefined based on prior recognition and knowledge of different typesand models of equipment used in the field, and what types and formats ofdata will be transmitted from those models of equipment. Therefore, theinterface module 40 is essentially “told” by the servers 105, 2305 whattypes of signals and data to expect from each type of equipment, suchthat the interface module can intake and normalize the receivedinformation accordingly.

In one embodiment, rather than being told by the servers 105, 2305 whattypes of data to expect from each type of EPSS equipment, the interfacemodule(s) 40 can auto-detect the type of equipment to which they areconnected. Generally, in this embodiment, the interface module(s) 40engage in an iterative process with the EPSS equipment to determine whattype of equipment the module(s) are connected to and what kinds ofsignals to expect from the equipment.

Continuing with discussion of step 3010 in FIG. 30A, once the interfacemodule(s) 40 understand what type of signals they will receive from eachtype of EPSS equipment, the modules can transform those signals intostandard, unified outputs for each category (e.g. ATS, generator, fuelsupply, etc.) of equipment. For example, received data may includevarying communication formats, be in different units, or be in differentregisters. Additionally, the data may need to be scaled to a commonvalue, or require some other type of transformation. Regardless, thesoftware included in the interface module(s) 40 is programmed to includethe intelligence to normalize the data into generic “ATS data” or“generator data” or some other standard type of data. Thus, all databeing output by the interface module 40 fits in a common category thatis easily recognizable by the management computer system 60.

Once the EPSS operational data has been normalized, the data isconverted into an acceptable delivery format (such as a data packet)(step 3015) and transmitted to the management computer system 60 (step3020). After it is received at the management computer system 60, thedata is further processed, stored, and displayed to system users viaterminals 45, 47, interface 55, reports, or some other presentationmechanism.

In addition to transmitting data from EPSS equipment to the managementcomputer system 60, the interface module(s) 40 also receive commandsfrom the servers 105, 2305 to carry out certain processes on the EPSSequipment. FIG. 30B is a flow chart showing the basic functionaloperations of one embodiment of the interface module 40 to receivetesting and control commands from the management computer system andtransmit those commands to the EPSS equipment. At step 3030, theinterface module 40 receives one or more control commands from theservers 105, 2305 within the management computer system 60. The commandsmay be for one or more items of EPSS equipment to which the interfacemodule 40 is connected to startup and begin operating for purposes of atest. Or, the commands may be to disable the EPSS equipment so thatmaintenance work may be performed on it. As will be understood,virtually any command relating to operation of the EPSS equipment iscontemplated within embodiments of the present system.

Regardless of the command or commands received by the interface module40, the module processes the commands into a format understandable bythe EPSS equipment (step 3035), and transmits those processed commandsto the EPSS equipment (step 3040) to carry out the desired function(s).In this way, a system user or operator may actively control specificitems of EPSS equipment remotely via the operative EPMS 10.

Testing EPSS Equipment Via Configured EPMS

As mentioned previously, it may be beneficial to routinely test EPSSequipment to ensure it is functioning properly in the event of anemergency. For some facilities (e.g. hospitals), frequent and routinetesting of EPSS equipment is required by federal agencies to receivefederal funding or even to continue operating. For example, the JointCommission (formerly JCAHO) requires each health care facility toimplement an emergency power testing program that includes generator 165load testing and overall EPSS maintenance. Along those lines, theNational Fire Protection Association (NFPA) establishes codes andstandards on the minimum testing requirements of EPSS equipment. Even ifnot required by a federal or state agency, many facilities actively wishto test their EPSS equipment so as to ensure that the equipment isoperating appropriately should it be needed during a power outage, orsimply to gather runtime performance data or reports.

Embodiments of an emergency power management system (EPMS) 10 asdescribed herein enable remote testing of EPSS equipment, real timeviewing of that equipment and associated testing data via a terminaldisplay while testing occurs, and generation of test reports forcompliance purposes or otherwise. Generally, there are four types oftests associated with embodiments of the present system automatic loadtests, automatic no load tests, manual load tests, and manual no loadtests. Additionally, in one embodiment, an emergency situation may beused as a test for compliance purposes. The details and processesassociated with these tests will be described in greater detail below.

Automatic Load Test

Generally, an automatic load test (ALT) is a test of one or more itemsof EPSS equipment that is initiated via a terminal display or userinterface in which the selected EPSS equipment is used to actually powera portion of a facility during the test. According to one embodiment, tobegin an ALT a system user simply clicks on the “Test Setup” button inthe test controls field 2530 of tabular EPSS view 2501 (shown in FIG.25A). When the “Test Setup” button is selected, a test setup screen 3100is displayed to a user via a terminal display, as shown in FIG. 31. Thetest setup screen 3100 includes selectable and finable parameter regionsfor setting the parameters that will be associated with a given test. Aswill be understood, the test setup screen 3100 may be accessed bynavigating through other displays and screens, and does not necessarilyhave to be accessed through test controls field 2530.

As shown in FIG. 31, test setup screen 3100 includes “Test Type” region3105 for selecting the type of test that will be initiated. Embodimentsof “Test Type” region 3105 may include a variety of tests, includingload and no load tests, recurring tests, one-time tests, and othersimilar types of tests. Test setup screen 3100 also includes “TestGroup” region 3110 which enables a user to select the specific EPSS,group of EPSS's, or specific items of EPSS equipment to be tested. “TestGroup” 3110 is beneficial because it provides a user the ability to testonly certain items of equipment within an EPSS (such as only half of theATS's 160, for example) rather than testing the entire EPSS.

Embodiments of the test setup screen 3100 also include an “InitiatingATS” region 3115 which allows a user to select a specific ATS 160 withina selected test group to initiate the test. For some compliance testingpurposes, it must be shown that each ATS 160 within an EPSS can startthe generator(s) 165 in the EPSS and switch the associated load togenerator power. Accordingly, embodiments of the EPMS 10 will store andmaintain a log of which ATS's 160 have been tested previously or mostrecently, and will “suggest” that an ATS that has not been used toinitiate a generator 165 recently be used to do so. As will beunderstood, a system user can override this suggestion if desired.

Further, after the “Initiating ATS” region 3115 has been set, the userthen fills in the “Load Test Transfer Time Offset” region 3120 and the“Transfer Block Size” region 3125. The “Load Test Transfer Time Offset”region 3120 corresponds to the time to delay (generally in seconds) thetransfer of subsequent ATS's 160 in the test group after the initiatingATS has switched. The “Transfer Block Size” region 3125 indicates thenumber of ATS's 160 that will start simultaneously after waiting for thetransfer time offset. As will be understood, these regions 3120, 3125will be inapplicable during a no load test because an ATS 160 is notused to actually switch from utility to emergency power during the test.As will also be understood, these regions 3120, 3125 will not apply whenonly a single ATS 160 is being tested.

Test setup screen 3100, as shown in FIG. 31, also includes 30% load ruleselectable region 3130, which enables a user to mandate whether thetested generator(s) 165 must reach 30% of their rated loads before thetest may continue. For compliance purposes, some agencies (e.g. NFPA)require that the tested generators 165 reach this 30% rated load valuebefore the test may be used as a valid test. When 30% load rule region3130 is selected, the EPMS 10 will wait to start the test until theassociated generator(s) 165 reach 30% of their rated load value. If,after a predetermined amount of time, the generator(s) 165 fail to reachthe 30% value, the test will be aborted and a notification alarm will besent to the system user. If the test does begin, but the load dropsbelow 30% at any time during the test, then the test will continue, buta similar notification alarm will be sent. As will be understood by oneof ordinary skill, while a 30% load value is discussed herein, otherrated load percentages may be used as testing parameters withinembodiments of the present system.

Once all testing parameters have been selected by the system user, theuser clicks “Next” button 3135 and returns to a terminal display (suchas tabular EPSS view 2501) that includes test controls field 2530. Theuser can then select the “Run Test” button within test controls field2530 to begin the selected test. Additionally, the user can view theselected EPSS equipment to be tested via a multimedia display 2562 priorto testing to ensure it is safe to proceed with testing. Once the “RunTest” button is selected, the test begins according to the selectedparameters in test setup screen 3100. While the test is occurring, livedata relating to all tested EPSS equipment is collected, stored, anddisplayed to a user in virtually real time via a terminal display, suchas any of the displays shown in FIGS. 24A-B, 25A-B, 26, and 27 discussedherein.

Referring now to FIG. 32, a flow chart is shown listing the stepsinvolved in one embodiment of a testing process 3200 for testing EPSSequipment. These steps will first be described in accordance with anautomatic load test. In one embodiment, once a test has been initiatedby a user via the test setup screen 3100 and corresponding “Run Test”button (or other similar controls), the management computer system 60detects that a pending test command has been generated (step 3205). Thesystem 60 then inserts a test record into a test log indicating a testhas been initiated. At step 3210 a, the system 60 checks to ensure thatan emergency situation is not occurring. If, at any point during a test,an emergency is detected, the system will abort the test and process theemergency event according to emergency process 3300 (described ingreater detail below).

After the management computer system 60 has verified that no emergencycurrently exists, the system moves to begin test step 3215. At step3215, the system 60 creates a database record including informationrelated to the test, such as a test title, the system user, the specificEPSS (or EPSS's) tested, the test group, the initiating ATS, an emailaddress of the user, and other similar information. The system 60 alsocreates a test record for each ATS 160 and each generator 165 beingtested. The ATS test record generally includes a unique test identifierfor the test, a definition of the server upon which the tested EPSS isdefined, and the given name of the ATS. The generator test recordgenerally includes similar information as the ATS test record, withadditional information related to engine run time hours. After theserecords have been created and the test start criterium have been met,the system 60 retrieves starting live values for EPSS operationalinformation and data, as well as other data, such as the start date andtime of the test.

Still referring to an embodiment of step 3215, after the system 60records the starting values for the EPSS equipment, the system thensends a start command through the interface module 40 to the initiatingATS to initiate the test. Once the system 60 detects a generator 165 isrunning, an entry is inserted into the test log indicating the starttime of the generator. The system 60 also generally detects and recordswhen all ATS's 160 have switched from utility to emergency power. Allassociated times (e.g. command received, test initiated, generatorrunning, ATS's switched over, etc.) are stored in a database 110, 2310for subsequent processing and reporting. In some embodiments, allgenerators 165 must have started and all ATS's 160 must have switched togenerator power in order for the collected data to qualify forcompliance testing purposes. Additionally, in some embodiments, ifcertain parameters are not met, then the test is aborted. For instance,if one or more of the generators fail to startup and begin running, orif one or more of the ATS's fail to switch over, then the test will beaborted and an alarm notification sent to the system user.

Still referring to FIG. 32, at step 3210 b the system 60 again checkswhether an emergency event is occurring. If so, then the test is abortedand emergency process 3300 is initiated. If not, then testing process3200 continues to step 3220, monitoring the test. During step 3220, thesystem collects all active EPSS operational data and displays the datato the user. The EPSS operational data is also continually recorded on adatabase 110, 2310 for use in generating subsequent operational andcompliance reports.

At step 3210 c, the system 60 again determines whether an emergency ispresent, and if none is, end test step 3225 of testing process 3200 isactivated. During end test step 3225, the system 60 logs a data recordas the final or end data record for the EPSS equipment in the test, andthen sends a stop command to the ATS's 160 to stop the test. The system60 then waits for the normal power breaker to close, and for all ATS's160 to retransfer back to utility power. The system 60 also waits forall generators 165 to stop running and cool down. Generally, themanagement computer system 60 will record the ATS retransfer time,generator stoppage time, generator cool down time, and any other similartimes as will occur to one of ordinary skill. Once all generators 165have cooled down, the system 60 processes the test data and generatesone or more test reports (step 3230) (discussed in greater detailbelow).

In some embodiments, the tested EPSS's will include only ATS's 160, andno generators 165. In these cases, the ATS's 160 may switch power toemergency power, but receive that emergency power from either agenerator or utility power feed from another EPSS. Thus, in some loadtest embodiments, only ATS's will be tested.

Automatic No Load Test

Generally, an automatic no load test (ANLT) is a test of one or moreitems of EPSS equipment that is initiated via a terminal display or userinterface in which the selected EPSS equipment to be tested does notactually power any portion of a facility during the test. Typically,during an automatic no load test only generators 165 are tested (i.e.ATS's 160 are not tested). Thus, in one embodiment, an ANLT follows thesame process and includes the same steps as the ALT described inconjunction with FIG. 32, except that power to the facility is nevertransferred from utility to generator power, and only data relating togenerators 165 is collected and stored. Additionally, to startup theitems of EPSS equipment that are part of the test, a signal is sentdirectly to the generator(s) 165 (via the interface module 40) ratherthan to the ATS's 160.

Manual Load Test

A manual load test (MLT) is similar to an automatic load test, exceptthat a manual load test is initiated physically at the specific items ofEPSS equipment to be tested rather than remotely through a terminaldisplay or user interface. Thus, in one embodiment, a MLT follows thesame process and includes the same steps as the ALT described inconjunction with FIG. 32, except that the EPSS equipment is physicallyactivated at the equipment by turning the equipment on. Specifically, inone embodiment, the test is initiated from a dry contact point at aninitiating ATS 160. Once the equipment has been activated, the testfollows the same steps and processes for an ALT as described in testingprocess 3200.

Manual No Load Test

A manual no load test (MNLT) is similar to an automatic no load test,except that a manual no load test is initiated physically at the itemsof EPSS equipment rather than remotely through a terminal display oruser interface. Just as with the MLT, the EPSS equipment in an MNLT isphysically activated at the equipment rather than via a command signalfrom the management computer system 60. However, unlike a MLT, the ATS's160 are not operated, and only the generator(s) 165 are turned on andtested. Once the generator(s) 165 have been activated, though, the MNLTfollows the same process as described above for the ANLT.

Emergency Process

As mentioned previously, many facilities either desire or are requiredto complete a multiplicity of performance and compliance tests on theirEPSS equipment every year. These tests can be a drain on time andresources due to the significant amount of fuel costs required tooperate the generator(s) 165, personnel needed to run the tests,equipment wear and tear, and other similar resources required tocomplete these tests. Accordingly, one embodiment of the present systemenables a facility to use an emergency or crisis event as one of itsnecessary or desired equipment tests. Traditionally, because emergenciesare unplanned and unexpected, there is no capability to record dataduring an emergency. In a present embodiment, however, because EPSS datais continuously monitored and recorded, once an emergency event occurs,the management computer system 60 initiates a test log to record EPSSoperational data during the emergency event. If the emergency eventlasts for an acceptable duration of time, then once normal power isrestored, the data collected during the even can be used as a load test.

Referring to FIG. 33, a flow chart listing the steps involved in anembodiment of an emergency process 3300 is shown. At step 3305, anemergency event is detected by the management computer system 60. Afterthe event has been detected, emergency event processing is begun 3310.During step 3310, a database record is created for the specificemergency similar to the database record created during test step 3215.Emergency records are also created for the generator(s) 165 and ATS's160 associated with the emergency event, similar to the test recordscreated during step 3215. During step 3315, EPSS operational data iscollected and stored in the emergency records for subsequent processinginto a test/emergency report. Once the emergency event ends, the system60 defines one of the final collected data points as the “final” datapoint for purposes of the test (step 3320). At step 3325, the EPSSoperational data collected during the emergency is processed in asimilar manner as the test data processed during step 3230, and the datais used to generate a test report for the given emergency.

Test Reporting

After the EPSS informational data has been collected during a testprocess 3200 or emergency process 3300, that data may be used togenerate a test report, examples of which are shown in FIGS. 34A-D and35A-D. Specifically, FIG. 34A is a sample generator operational report3401 for a test of a given generator 165 within an EPSS at a facility.As shown, the report 3401 includes a general informational field 3410with basic information regarding the reported test, such as the systemoperator, site, test ID, and other similar information. In theembodiment shown, the generator operational report 3401 further includesa “Pre-Test Checklist” field 3412 detailing that certain items werechecked before the test, such as whether the EPSS main circuit breakerwas closed, whether protective equipment was utilized, and other similaritems. The report 3401 also includes a generator information field 3414that lists the location, manufacturer, model, rated power, 30% ratedpower, and other information related to the specific generator 165.Additionally, in one embodiment, the generator information field 3414shows various time measurements for the specific generator 165 duringthe given test, such as the engine crank time, engine cool down time,total run time, beginning engine hours, ending engine hours, and othersimilar measurements as will be apparent to one having ordinary skill.

Also included in the generator operational report 3401 shown in FIG. 34Aare generator data field 3416 and engine data field 3418. The generatordata field 3416 includes data related to the electrical generator forthe particular genset, including voltage measures, current measures,three phase power, percent rated power capacity, and frequency for threediscrete data points collected during the test. For compliance purposes,tests are generally required to include three data points—the beginningof the test, midpoint of the test, and end of the test. Thus, the threeseparate rows shown in generator data field 3416 correspond to theserequired data points. As will be understood, many more data points withmany other generator values may be reported in generator operationalreport 3401 as desired by a system user.

Generator operational report 3401 also comprises an engine data field3418 showing data related to the engine (mechanical power source) forthree discrete data points collected during the test. The data shown inthe engine data field 3418 in FIG. 34A includes battery charger voltageand current, oil pressure, coolant temperature, and exhaust temperature,but may include any other collected values the system user deemsimportant.

FIG. 34B is a sample generator compliance report 3402 generated from thesame data collected and used in the generator operational report 3401.The compliance report 3402 includes many of the same fields and valuesas the operational report 3401, except that because the compliancereport is created for purposes of regulatory compliance, it must meetcertain standards or guidelines. The generator operational report 3401,on the other hand, is a useful report for the facility's own benefit,and thus the information may be displayed in any form the user desires.In the embodiment of the compliance report 3402 shown in FIG. 34B, the“Pre-Test Checklist” field 3412 has been omitted, as well as some of theinformation from the generator information field 3414 that was includedin generator operational report 3401. Also, the generator data andengine data fields 3416, 3418, have been combined to show one, cohesivereport of required generator statistics. The generator data field 3420shown in FIG. 34B includes the three phase voltage and current for thegenerator 165 during the test, as well as the frequency and exhausttemperatures. As will be understood, the generator data field 3420 mayinclude any other measures that are required for compliance purposeswith varying regulatory bodies.

FIG. 34C illustrates a sample ATS operational report 3403 for a test ofseveral ATS's 160 within an EPSS according to an embodiment of thepresent system. As shown, the operational report 3403 includes agraphical timeline 3430 showing the time between certain events duringthe test. For example, graphical timeline 3430 indicates the time atwhich the test was detected, when the engines of the generator 165 beganrunning, when emergency power reached a necessary voltage to supply theload, when the ATS's 160 switched to emergency power, and when the testended. For many facilities, the transfer time between utility andemergency power, or the time the generators require until they areproducing sufficient power, or many other time measures are important tothe efficiency and viability of the EPSS's at a facility. As will beunderstood, other times and events other than those shown in FIG. 34Cmay be listed in graphical timeline 3430.

The ATS operational report 3403 also includes ATS data display regions3435 for each tested ATS that detail information related to the testedATS's 160, including the three phase voltage, current, and percentage ofrated current achieved at three discrete times during the test. Again,just as with generator reports 3401, 3402, it may be important for somecompliance requirements to have three discrete data points at thebeginning, middle, and end of a test. In the embodiment shown, ATS datadisplay regions 3435 also include transfer delay and retransfer delaytimes, as well as other information related to each ATS, such as themanufacturer, location of the ATS, etc.

Turning now to FIG. 34D, a sample ATS compliance report 3404 is shownfor a test of several ATS's 160 within an EPSS according to anembodiment of the present system. As shown, the tested ATS's 160 arelisted in “ATS Description” region 3442, the physical location of eachtested ATS is shown in “Location” region 3444, and the specific loadcontrolled by each ATS is described in “Service” region 3446. Also,switch time region 3448 lists the time at which each ATS 160 switched toemergency power and when each ATS switched back to normal power duringthe test. As will be understood, other measures may be included incompliance report 3404 for each tested ATS 160 depending on theregulatory compliance requirements of each separate facility.

FIGS. 35A-D illustrate examples of other testing reports that may begenerated by embodiments of the present system. FIG. 35A is an emergencyevents report 3501 listing emergency events that have occurred for eachgenerator 165 at a facility over a given time period. As shown, eachgenerator 165 is listed, as well as a start date and end date for eachemergency experienced by each generator over the selected time period.Additionally, the engine start hours and engine end hours for eachgenerator 165 are shown (i.e. the total run time the generator hasexperienced over its lifetime), as well as any comments relating to theemergencies. As will be understood, an emergency events report 3501 maybe generated for any desired period of time. As will also be understood,a report 3501 may include only one of a facility's generators, or aselected grouping of generators, or all of the generators at thefacility.

FIG. 35B shows a sample generator loaded runs report 3502 listing allloaded uses of each generator 165 at a facility over a given timeperiod. The loaded uses may include manual and automatic tests, as wellas emergencies. The embodiment of the loaded runs report 3502 shown inFIG. 35B includes the run type (i.e. MLT, ALT, or emergency) for eachloaded use, as well as the run date, prior run date, and days betweenthese dates. The report also shows which (if any) of the loaded runsfall outside of a 20-40 day window between the prior loaded run for thegiven generator 165. For some compliance requirements (e.g. The JointCommission), this 20-40 day loaded run window must be tracked andreported to retain federal compliance. As will be understood, thegenerator loaded runs report 3502 may include any other measures orvalues collected by the EPMS 10 for any generator loaded runs over thegiven time period.

FIG. 35C is a sample generator run times report 3503 showing all runtimes of each generator at a facility over a given time period. Asshown, the generator run times report 3503 includes the total runninghours for no load tests and load tests of each generator over the giventime span. The report 3503 also includes emergency running hours and anyother loaded run hours for the time period. The embodiment of the report3503 further shows the total run time hours for each generator for thegiven time period.

FIG. 35D illustrates a sample switch operation report 3504 listing alltransfers between normal and emergency power for one or more ATS's 160at a facility over a given time period. As shown, listed under each ATS160 is each transfer between emergency and normal power for that ATSover the predefined time period, whether that ATS was the ATS thatinitiated the transfer or test, the date and time of each transfer, andthe type of power disruption event that was associated with eachtransfer. Further, comments may be inserted for each transfer at thesystem user's discretion. As will be understood, as few as one or asmany as all the ATS's 160 at a given facility may be included in aswitch operation report 3504.

As will be understood, all of the reports described in association withFIGS. 34A-D and 35A-D may be printed and viewed on paper, or viewed on acomputer screen or terminal display, or used via some other similarmechanism.

According to another aspect of the present system, an interactivecalendar display 3600 is provided via a terminal 45, 47 or graphicaluser interface for displaying future scheduled tests and past powerdisruption events. An embodiment of the calendar display is shown inFIG. 36. As shown, the calendar display 3600 includes live links 3605 topast or future power disruption events. By clicking on a live link 3605,a user can view one or more test reports for that test (if it is a priortest or emergency), or view and edit the setup and parameters for afuture scheduled test. As one having ordinary skill in the art willunderstand, the interactive calendar display 3600 may show events for aspecific generator 165 or ATS 160, or a specific EPSS, or even an entirefacility or facilities. Additionally, the calendar display 3600 mayprovide a weekly view, monthly view, yearly view, or any other time spanthe user desires.

The following appendices are intended to be included as part of thedisclosure contained herein and are included for purposes of aiding inthe understanding of the embodiments and aspects presented in thisdisclosure. These appendices are not intended to limit the disclosedembodiments and aspects in any way, and are included for illustrativepurposes only.

The foregoing description of the exemplary embodiments has beenpresented only for the purposes of illustration and description and isnot intended to be exhaustive or to limit the inventions to the preciseforms disclosed. Many modifications and variations are possible in lightof the above teaching.

The embodiments were chosen and described in order to explain theprinciples of the inventions and their practical application so as toenable others skilled in the art to utilize the inventions and variousembodiments and with various modifications as are suited to theparticular use contemplated. Alternative embodiments will becomeapparent to those skilled in the art to which the present inventionspertains without departing from its spirit and scope. Accordingly, thescope of the present inventions is defined by the appended claims ratherthan the foregoing description and the exemplary embodiments describedtherein.

1-92. (canceled)
 93. An emergency power management system (EPMS) forproviding predictive analyses related to one or more pre-existingemergency power supply systems (EPSS's), comprising: a plurality ofitems of data acquisition equipment for collecting EPSS operationalinformation from one or more items of EPSS equipment, wherein the one ormore items of EPSS equipment are manufactured by one or moremanufacturers; one or more interface modules operatively connected tothe plurality of items of data acquisition equipment for normalizing theEPSS operational information for subsequent processing; a managementcomputer system operatively connected to the one or more interfacemodules for receiving the normalized EPSS operational information fromthe one or more interface modules, the management computer systemcomprising automatically configurable management software for carryingout the computer-implemented steps of: storing the normalized EPSSoperational information in a database within the management computersystem; tracking one or more occurrences in the stored EPSS operationalinformation over time for determining trends in the EPSS operationalinformation; and generating one or more predictive reports foranticipated future occurrences based on the one or more trackedoccurrences related to the one or more items of EPSS equipment.
 94. Themethod of claim 93, wherein the one or more occurrences that are trackedby the automatically configurable management software are predefined bya system user.
 95. The system of claim 93, wherein the one or moretracked occurrences in the stored EPSS operational information comprisedates of utility power outages.
 96. The system of claim 95, wherein theone or more predictive reports for anticipated future occurrencescomprise one or more times of a year when utility power outages are morelikely to occur.
 97. The system of claim 93, wherein the one or moretracked occurrences in the stored EPSS operational information comprisedurations of utility power outages.
 98. The system of claim 97, whereinthe one or more predictive reports for anticipated future occurrencescomprise a typical length of a utility power outage.
 99. The system ofclaim 93, wherein the one or more tracked occurrences in the stored EPSSoperational information comprise failures of particular manufacturermodels of items of EPSS equipment.
 100. The system of claim 99, whereinthe one or more predictive reports for anticipated future occurrencescomprise average failure rates of the particular manufacturer models ofthe items of EPSS equipment.
 101. The system of claim 93, wherein theone or more tracked occurrences in the stored EPSS operationalinformation comprise battery failures of the items of EPSS equipment.102. The system of claim 101, wherein the one or more predictive reportsfor anticipated future occurrences comprise average failure rates ofbatteries.
 103. The system of claim 93, further comprising the step ofdisplaying the one or more predictive reports to a system user via auser interface.
 104. The system of claim 93, wherein the one or morepredictive reports for anticipated future occurrences includes one ormore suggestions for preparing for future occurrences related to the oneor more items of EPSS equipment.
 105. The system of claim 93, whereinthe plurality of items of data acquisition equipment are selected fromthe group comprising: monitoring sensors, connectors required byparticular types of monitoring sensors, power supplies, fuel gauges,power meters, gauges, status indicators, viewing cameras, microphones,vibration sensors, inertial sensors, motion sensors, actuationcomponents, solenoids, and relays.
 106. The system of claim 105, whereinthe monitoring sensors are selected from the group comprising:thermocouples, resistive temperature detectors (RTDs), pressure senders,current transformers (CTs), and limit switches.
 107. The system of claim93, wherein the plurality of items of data acquisition equipment arephysically installed on the one or more items of EPSS equipment. 108.The system of claim 93, wherein the one or more items of EPSS equipmentare preconfigured to include one or more of the plurality of items ofdata acquisition equipment.
 109. The system of claim 93, wherein the oneor more items of EPSS equipment are selected from the group comprising:generators, automatic transfer switches (ATS's), switchgear, fuelsupplies, and fuel management systems.
 110. The system of claim 109,wherein the EPSS operational information for each generator within theone or more pre-existing EPSS's is selected from the group comprising:jacket water temperature, exhaust temperature, oil pressure, oiltemperature, coolant temperature, battery charging voltage, batterycharging current, engine running status, engine “not in auto” status,engine runtime, engine speed, generator power, rated load, generatorpower factor, percent generator capacity, three-phase voltage,three-phase current, generator frequency, and applied torque.
 111. Thesystem of claim 109, wherein the EPSS operational information for eachATS within the one or more pre-existing EPSS's is selected from thegroup comprising: emergency power, emergency power factor, emergencyfrequency, emergency three-phase voltage, emergency three-phase current,emergency average current, emergency power hours, normal power, normalpower factor, normal frequency, normal three-phase voltage, normalthree-phase current, normal average current, normal power hours,emergency power status, normal power status, emergency breaker status,and normal breaker status.
 112. The system of claim 109, wherein theEPSS operational information for each fuel supply within the one or morepre-existing EPSS's is selected from the group comprising: fuel level,fuel supply status, and exit fuel flow rate.
 113. The system of claim93, wherein each of the one or more interface modules includes afirewall for preventing unauthorized access to the one or more items ofEPSS equipment, the management computer system, and the EPSS operationalinformation.
 114. The system of claim 93, wherein the managementcomputer system further includes one or more servers for operating theautomatically configurable management software.
 115. The system of claim93, wherein the automatically configurable management software comprisessupervisory control and data acquisition (SCADA) software. 116-219.(canceled)